Local kernel data corruption via full PHY array
Published May 24, 2024 · Updated May 11, 2026
Out-of-bounds access in the Linux kernel de4x5 Ethernet driver allows local users to alter kernel data or interrupt service. During generic MII discovery, mii_get_phy lets k reach eight after scanning a full lp->phy array, then writes address, identifier, and speed-control fields through the invalid slot. Reachability requires the de4x5 driver and a device state in which all eight PHY records already have nonzero identifiers.
Summary
What happened
Out-of-bounds access in the Linux kernel de4x5 Ethernet driver allows local users to alter kernel data or interrupt service. During generic MII discovery, mii_get_phy lets k reach eight after scanning a full lp->phy array, then writes address, identifier, and speed-control fields through the invalid slot. Reachability requires the de4x5 driver and a device state in which all eight PHY records already have nonzero identifiers.
The record
- CVE
- CVE-2021-47547
- Published
- May 24, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 24, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <12f907cb11576b8cd0b1d95a16d1f10ed5bb7237
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <142ead3dc70411bd5977e8c47a6d8bf22287b3f8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2c1a6a9a011d622a7c61324a97a49801ba425eff
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <61217be886b5f7402843677e4be7e7e83de9cb41
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <77ff166909458646e66450e42909e0adacc99049
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d3dedaa5a601107cfedda087209772c76e364d58
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ec5bd0aef1cec96830d0c7e06d3597d9e786cc98
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f059fa40f0fcc6bc7a12e0f2a2504e9a4ff74f1f
- Affected versionversion=2.6.12
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