Kernel crash via stale driver pointer cleanup
Published Oct 21, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel PHY subsystem allows local users to crash the kernel after a driver probe fails. In phy_attach_direct(), a failed probe leaves dev->driver set even though knode_driver was never added to its klist, so device deletion calls klist_remove() on an uninitialized list node. Triggering the fault requires local low-privileged access and a PHY-driver probe failure; the demonstrated consequence is a kernel crash, with no reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in the Linux kernel PHY subsystem allows local users to crash the kernel after a driver probe fails. In phy_attach_direct(), a failed probe leaves dev->driver set even though knode_driver was never added to its klist, so device deletion calls klist_remove() on an uninitialized list node. Triggering the fault requires local low-privileged access and a PHY-driver probe failure; the demonstrated consequence is a kernel crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2022-49021
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=2.6.14
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <0744c7be4de564db03e24527b2e096b7e0e20972
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <369eb2c9f1f72adbe91e0ea8efb130f0a2ba11a6
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <3e21f85d87c836462bb52ef2078ea561260935c1
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <51d7f6b20fae8bae64ad1136f1e30d1fd5ba78f7
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <7730904f50c7187dd16c76949efb56b5fb55cd57
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <8aaafe0f71314f46a066382a047ba8bb3840d273
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <eaa5722549ac2604ffa56c2e946acc83226f130c
- Affected versionversion=e13934563db047043ccead26412f552375cea90c <fe6bc99c27c21348f548966118867ed26a9a372c
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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