Service interruption via leaked PHY allocations
Published May 1, 2025 · Updated May 11, 2026
Memory leakage in the Linux kernel DSA loop driver allows local users to interrupt service during module initialization. The dsa_loop_init() error path returns after mdio_driver_register() fails without releasing PHY devices, while fixed_phy_unregister() removes but does not free each allocation. Repeated initialization failures can consume kernel memory; exploitation requires low-privileged local access and the DSA loop driver.
Summary
What happened
Memory leakage in the Linux kernel DSA loop driver allows local users to interrupt service during module initialization. The dsa_loop_init() error path returns after mdio_driver_register() fails without releasing PHY devices, while fixed_phy_unregister() removes but does not free each allocation. Repeated initialization failures can consume kernel memory; exploitation requires low-privileged local access and the DSA loop driver.
The record
- CVE
- CVE-2022-49926
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 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=4.12
- Affected versionversion=98cd1552ea27e512c7e99e2aa76042a26e4fb25c <37a098fc9b42bd7fce66764866aa514639667b6e
- Affected versionversion=98cd1552ea27e512c7e99e2aa76042a26e4fb25c <4d2024b138d9f7b02ae13ee997fd3a71e9e46254
- Affected versionversion=98cd1552ea27e512c7e99e2aa76042a26e4fb25c <633efc8b3dc96f56f5a57f2a49764853a2fa3f50
- Affected versionversion=98cd1552ea27e512c7e99e2aa76042a26e4fb25c <935b4beb724946a37cebf97191592d4879d3a3a3
- Affected versionversion=98cd1552ea27e512c7e99e2aa76042a26e4fb25c <9f555b1584fc2d5d16ee3c4d9438e93ac7c502c7
- Affected versionversion=98cd1552ea27e512c7e99e2aa76042a26e4fb25c <bbc5d7b46a729bfcbb5544f6612b7a67dd4f4d6f
- Affected versionversion=98cd1552ea27e512c7e99e2aa76042a26e4fb25c <d593e1ede655b74c42e4e4fe285ea64aee96fb5c
What conditions does exploitation require?
What is affected?
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