Kernel crash via uninitialized bridge removal
Published Sep 15, 2025 · Updated Sep 15, 2025
NULL pointer dereference in Linux's MegaChips bridge driver allows local users to crash the kernel during driver removal. The stdp4028_ge_b850v3_fw_remove path calls drm_bridge_remove for an object left uninitialized when stdp2690 and stdp4028 do not probe together. Reaching the fault requires the affected bridge configuration and execution of the driver-removal path; the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in Linux's MegaChips bridge driver allows local users to crash the kernel during driver removal. The stdp4028_ge_b850v3_fw_remove path calls drm_bridge_remove for an object left uninitialized when stdp2690 and stdp4028 do not probe together. Reaching the fault requires the affected bridge configuration and execution of the driver-removal path; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2022-50317
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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.
- Affected versionversion=11632d4aa2b3f126790e81a4415d6c23103cf8bb <1ff673333d46d2c1b053ebd0c1c7c7c79e36943e
- Affected versionversion=11632d4aa2b3f126790e81a4415d6c23103cf8bb <21764467ab396d9f08921e0a5ffa1214244e1ad9
- Affected versionversion=11632d4aa2b3f126790e81a4415d6c23103cf8bb <7371fad5cfe6eada6bb5523c895fd6074b15c2b9
- Affected versionversion=16e3827904932eccfba0915f0c93b519de3536ac <5bc20bafcd87ba0858ab772cefc7047cb51bc249
- Affected versionversion=405856460d3e7aefb7c1aef047ec88fc4ef2e2a5 <4610e7a4111fa3f3ce27c09d6d94008c55f1cd31
- Affected versionversion=50ad94f8654a53ec9ca3604a7a23cbaf166e0119 <1daf69228e310938177119c4eadcd30fc75c81e0
- Affected versionversion=5.17
- Affected versionversion=7649972d97fb98578fbc4a351416cf72895e7c4d <aaa512ad1e59f2edf8a9e4f2b167a44b24670679
- Affected versionversion=b8d10f601f226f055df8b5368d7ea7f369136cd5 <877e92e9b1bdeb580b31a46061005936be902cd4
- Affected versionversion=e449461989f0674f188d30494ffd3f5ba74c1a05
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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