CVE-2022-50878

Kernel crash via premature bridge encoder dereference

Published Dec 30, 2025 · Updated Dec 30, 2025

NULL pointer dereference in the Lontium LT9611 bridge driver in affected Linux kernel releases allows attackers to crash the kernel. The lt9611_connector_init function passes bridge->encoder to drm_connector_attach_encoder before verifying that the pointer is non-NULL. Reachability requires initialization of an LT9611 display bridge with no encoder; published upstream material does not establish attacker control over that state.

CVSS severity4.3
Medium
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

NULL pointer dereference in the Lontium LT9611 bridge driver in affected Linux kernel releases allows attackers to crash the kernel. The lt9611_connector_init function passes bridge->encoder to drm_connector_attach_encoder before verifying that the pointer is non-NULL. Reachability requires initialization of an LT9611 display bridge with no encoder; published upstream material does not establish attacker control over that state.

The record

CVE
CVE-2022-50878
Published
Dec 30, 2025
Updated
Dec 30, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
physical
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 30, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 30, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3959e8faf8bf6bea619e8856c736db64e6eced37
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <912f84e15e94ab87f5a7156aa1870090373d8304
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a29f7427041a943484f916157c43c46d3bbf25d4
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b2e4323e0020213f44dca6ffc815d66aef39f6f6
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ef8886f321c5dab8124b9153d25afa2a71d05323

What conditions does exploitation require?

Attack vectorphysical
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3959e8faf8bf6bea619e8856c736db64e6eced37; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <912f84e15e94ab87f5a7156aa1870090373d8304; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a29f7427041a943484f916157c43c46d3bbf25d4; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b2e4323e0020213f44dca6ffc815d66aef39f6f6; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ef8886f321c5dab8124b9153d25afa2a71d05323

Published CVSS scores

4.3Amazon LinuxCVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo