Service interruption via leaked PHY device references
Published Sep 4, 2024 · Updated May 11, 2026
Memory leakage in Linux kernel 5.10 through 6.10.4 allows local users to interrupt service through Broadcom SF2 MDIO registration. The bcm_sf2_mdio_register() cleanup loop calls of_phy_find_device(), which increments each PHY device reference, but removes the device without a balancing put_device(). Local access and a Broadcom SF2 DSA configuration are required; accumulated references consume kernel memory without reported data access or modification.
Summary
What happened
Memory leakage in Linux kernel 5.10 through 6.10.4 allows local users to interrupt service through Broadcom SF2 MDIO registration. The bcm_sf2_mdio_register() cleanup loop calls of_phy_find_device(), which increments each PHY device reference, but removes the device without a balancing put_device(). Local access and a Broadcom SF2 DSA configuration are required; accumulated references consume kernel memory without reported data access or modification.
The record
- CVE
- CVE-2024-44971
- Published
- Sep 4, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 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=5.10
- Affected versionversion=771089c2a485958e423f305e974303760167b45c <7feef10768ea71d468d9bbc1e0d14c461876768c
- Affected versionversion=771089c2a485958e423f305e974303760167b45c <a7d2808d67570e6acae45c2a96e0d59986888e4c
- Affected versionversion=771089c2a485958e423f305e974303760167b45c <b7b8d9f5e679af60c94251fd6728dde34be69a71
- Affected versionversion=771089c2a485958e423f305e974303760167b45c <c05516c072903f6fb9134b8e7e1ad4bffcdc4819
- Affected versionversion=771089c2a485958e423f305e974303760167b45c <e3862093ee93fcfbdadcb7957f5f8974fffa806a
- Affected versionversion=771089c2a485958e423f305e974303760167b45c <f3d5efe18a11f94150fee8b3fda9d62079af640a
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