System crash via empty MDIO-bus list
Published Jul 30, 2024 · Updated Aug 5, 2026
Improper exceptional-condition handling in affected Linux kernel releases allows local users to crash the system through an empty MDIO-bus list. mv88e6xxx_default_mdio_bus uses list_first_entry and then tests its result for NULL, although that helper does not return NULL for an empty chip->mdios list. The published record does not document how a local user reaches the empty-list state, and the fix was compile-tested only.
Summary
What happened
Improper exceptional-condition handling in affected Linux kernel releases allows local users to crash the system through an empty MDIO-bus list. mv88e6xxx_default_mdio_bus uses list_first_entry and then tests its result for NULL, although that helper does not return NULL for an empty chip->mdios list. The published record does not document how a local user reaches the empty-list state, and the fix was compile-tested only.
The record
- CVE
- CVE-2024-42224
- Published
- Jul 30, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-754, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.11
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <2a2fe25a103cef73cde356e6d09da10f607e93f5
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <3bf8d70e1455f87856640c3433b3660a31001618
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <3f25b5f1635449036692a44b771f39f772190c1d
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <47d28dde172696031c880c5778633cdca30394ee
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <4c7f3950a9fd53a62b156c0fe7c3a2c43b0ba19b
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <8c2c3cca816d074c75a2801d1ca0dea7b0148114
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <aa03f591ef31ba603a4a99d05d25a0f21ab1cd89
- Affected versionversion=a3c53be55c955b7150cda17874c3fcb4eeb97a89 <f75625db838ade28f032dacd0f0c8baca42ecde4
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