Service interruption via leaked MDIO device memory
Published May 21, 2024 · Updated May 11, 2026
Memory leak in the MDIO bus interface in affected Linux kernel releases allows local users to interrupt service via registration failures. __mdiobus_register() leaves bus->state as MDIOBUS_ALLOCATED after device_register() runs, so mdiobus_free() calls kfree() instead of put_device() on failure. Exploitation requires local low-privileged access, and the published assessment limits the consequence to availability without data exposure or modification.
Summary
What happened
Memory leak in the MDIO bus interface in affected Linux kernel releases allows local users to interrupt service via registration failures. __mdiobus_register() leaves bus->state as MDIOBUS_ALLOCATED after device_register() runs, so mdiobus_free() calls kfree() instead of put_device() on failure. Exploitation requires local low-privileged access, and the published assessment limits the consequence to availability without data exposure or modification.
The record
- CVE
- CVE-2021-47416
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 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.28
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <064c2616234a7394867c924b5c1303974f3a4f4d
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <0d2dd40a7be61b89a7c99dae8ee96389d27b413a
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <2250392d930bd0d989f24d355d6355b0150256e7
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <2397b9e118721292429fea8807a698e71b94795f
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <25e9f88c7e3cc35f5e3d3db199660d28a15df639
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <414bb4ead1362ef2c8592db723c017258f213988
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <ca6e11c337daf7925ff8a2aac8e84490a8691905
- Affected versionversion=46abc02175b3c246dd5141d878f565a8725060c9 <f4f502a04ee1e543825af78f47eb7785015cd9f6
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