CVE-2022-50878
Description
In the Linux kernel, the following vulnerability has been resolved:
gpu: lontium-lt9611: Fix NULL pointer dereference in lt9611_connector_init()
A NULL check for bridge->encoder shows that it may be NULL, but it already been dereferenced on all paths leading to the check. 812 if (!bridge->encoder) {
Dereference the pointer bridge->encoder. 810 drm_connector_attach_encoder(<9611->connector, bridge->encoder);
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A NULL pointer dereference in the Linux kernel's Lontium LT9611 driver can cause a crash when the bridge encoder is NULL but is dereferenced before being checked.
Vulnerability
In the Linux kernel, a NULL pointer dereference vulnerability exists in the lt9611_connector_init() function of the Lontium LT9611 GPU driver. The root cause is that the code dereferences bridge->encoder at line 810 via drm_connector_attach_encoder(), but only checks for a NULL value at line 812. This means if bridge->encoder is NULL, the driver will crash before the check is reached [1][2].
Exploitation
An attacker would need to trigger the initialization of the LT9611 connector in a context where the bridge encoder has not been properly set. This could occur on systems using the LT9611 bridge chip, possibly through hot-plug events or driver binding sequences that leave the encoder pointer uninitialized. No special privileges are required beyond local access to trigger the driver path, but the attack surface is limited to systems with the affected hardware.
Impact
Successful exploitation leads to a kernel NULL pointer dereference, resulting in a system crash (denial of service). The vulnerability does not appear to allow privilege escalation or arbitrary code execution based on the available information.
Mitigation
The fix has been applied in the Linux kernel stable tree. Users should update to a kernel version containing the commit that moves the NULL check before the dereference. No workaround is documented, but ensuring the bridge encoder is always initialized before connector before initialization can prevent the issue.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
53959e8faf8bfa29f7427041ab2e4323e0020912f84e15e94ef8886f321c5Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
5- git.kernel.org/stable/c/3959e8faf8bf6bea619e8856c736db64e6eced37nvd
- git.kernel.org/stable/c/912f84e15e94ab87f5a7156aa1870090373d8304nvd
- git.kernel.org/stable/c/a29f7427041a943484f916157c43c46d3bbf25d4nvd
- git.kernel.org/stable/c/b2e4323e0020213f44dca6ffc815d66aef39f6f6nvd
- git.kernel.org/stable/c/ef8886f321c5dab8124b9153d25afa2a71d05323nvd
News mentions
0No linked articles in our index yet.