Kernel crash via unchecked driver data dereference
Published Feb 26, 2025 · Updated May 11, 2026
NULL pointer dereference in the Micrel PHY driver in Linux allows local users to crash the kernel during device probing. Micrel PHY setup paths dereference priv->type without checking whether a phy_driver supplies driver_data alongside its probe callback. Reachability requires local access and an affected Micrel PHY probe configuration; the resulting fault interrupts the host without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in the Micrel PHY driver in Linux allows local users to crash the kernel during device probing. Micrel PHY setup paths dereference priv->type without checking whether a phy_driver supplies driver_data alongside its probe callback. Reachability requires local access and an affected Micrel PHY probe configuration; the resulting fault interrupts the host without reported data disclosure or modification.
The record
- CVE
- CVE-2022-49472
- Published
- Feb 26, 2025
- 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
- Feb 26, 2025CVE 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=3.19
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <143878e18001c5a61fcc7ae5c5240323753bb641
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <1e5fbfc2a6f384e3195446c14bbd3bc298eb88c2
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <660dfa033ccc9afb032015b6dc76e846bba42cfb
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <7dcb404662839a4ed1a9703658fee979eb894ca4
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <91e720b32cba25fa58eaa4c88fe957009cffe9f3
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <abb5594ae2ba7b82cce85917cc6337ec5d774837
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <bd219273b4e004a3f853da72e111fc8f81357501
- Affected versionversion=e6a423a81da0eb3da755428f4d2df5a9ba13030f <f2ef6f7539c68c6bd6c32323d8845ee102b7c450
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