LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50317: drm/bridge: megachips: Fix a null pointer dereference bug

In the Linux kernel, the following vulnerability has been resolved: drm/bridge: megachips: Fix a null pointer dereference bug When removing the module we will get the following warning: [ 31.911505] i2c-core: driver [stdp2690-ge-b850v3-fw] unregistered [ 31.912484] general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI [ 31.913338] KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] [ 31.915280] RIP: 0010:drm_bridge_remove+0x97/0x130 [ 31.921825] Call Trace: [ 31.922533] stdp4028_ge_b850v3_fw_remove+0x34/0x60 [megachips_stdpxxxx_ge_b850v3_fw] [ 31.923139] i2c_device_remove+0x181/0x1f0 The two bridges (stdp2690, stdp4028) do not probe at the same time, so the driver does not call ge_b850v3_resgiter() when probing, causing the driver to try to remove the object that has not been initialized. Fix this by checking whether both the bridges are probed.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50317 is a Linux kernel bug in the Megachips DRM bridge driver. Under specific driver removal conditions, the kernel can hit a null pointer dereference and fault. Business impact is most likely availability on systems using this driver, not broad internet exposure.

Executive priority

Treat as a targeted kernel stability issue. Patch through normal Linux kernel maintenance, with higher priority for embedded, display, or hardware platforms using this Megachips bridge driver. It does not currently justify emergency enterprise-wide response absent confirmed exposure.

Technical view

The bug affects the megachips stdp2690/stdp4028 GE B850v3 firmware bridge path. If both bridges are not probed, removal may call drm_bridge_remove on an uninitialized object, causing a null pointer dereference/general protection fault. The fix checks whether both bridges are probed before removal handling.

Likely exposure

Exposure appears limited to Linux systems with the affected Megachips DRM bridge driver present and relevant hardware or module use. General servers without this driver or hardware are unlikely to be exposed. The source bundle lists multiple Linux stable branches and commits, but no CVSS score.

Exploitation context

The described trigger is module removal when the paired bridges did not both initialize. The bundle does not report remote exploitation, privilege impact, or public weaponization. CISA KEV status is false, so active exploitation should not be assumed.

Researcher notes

The CVE record identifies the resolved condition and stable commits but provides no CVSS, CWE, exploitability analysis, or distribution-specific fixed package versions. Validation should focus on driver reachability, module lifecycle behavior, and whether downstream kernels backported the probe-check fix.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Prioritize systems using Megachips stdp2690/stdp4028 bridge drivers.
  • If not required, avoid loading or unloading the affected module until patched.
  • Follow your Linux distribution’s advisory and kernel backport guidance.

Validation and detection

  • Inventory kernel versions against vendor advisories and listed stable fixes.
  • Check whether the Megachips bridge driver is built, loaded, or packaged.
  • Confirm the relevant stable commit is present in your kernel source or changelog.
  • Review kernel logs for null pointer dereference or general protection faults during module removal.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50317 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7649972d97fb98578fbc4a351416cf72895e7c4d, 16e3827904932eccfba0915f0c93b519de3536ac, 50ad94f8654a53ec9ca3604a7a23cbaf166e0119, b8d10f601f226f055df8b5368d7ea7f369136cd5, 405856460d3e7aefb7c1aef047ec88fc4ef2e2a5, 11632d4aa2b3f126790e81a4415d6c23103cf8bb, 11632d4aa2b3f126790e81a4415d6c23103cf8bb, 11632d4aa2b3f126790e81a4415d6c23103cf8bb, e449461989f0674f188d30494ffd3f5ba74c1a05unaffected
LinuxLinux5.17, 0, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.