Local service interruption via device-node refcount leak
Published Feb 26, 2025 · Updated May 11, 2026
Reference-count leak in Linux 4.20 through branch-specific fixes allows local users to interrupt service through GSWIP probe failures. The gswip_gphy_fw_list function exits its child-node loop after a failed firmware probe without releasing gphy_fw_np, retaining a device-tree node reference. A Lantiq GSWIP device-tree configuration and low-privilege local access are required, but the public record does not disclose how the user triggers the failing probe.
Summary
What happened
Reference-count leak in Linux 4.20 through branch-specific fixes allows local users to interrupt service through GSWIP probe failures. The gswip_gphy_fw_list function exits its child-node loop after a failed firmware probe without releasing gphy_fw_np, retaining a device-tree node reference. A Lantiq GSWIP device-tree configuration and low-privilege local access are required, but the public record does not disclose how the user triggers the failing probe.
The record
- CVE
- CVE-2022-49346
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 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=14fceff4771e51b23b4485b575cf9e5b3414b89b <0737e018a05e2aa352828c52bdeed3b02cff2930
- Affected versionversion=14fceff4771e51b23b4485b575cf9e5b3414b89b <2e007ac6fa7c9c94ad84da075c5c504afad690a0
- Affected versionversion=14fceff4771e51b23b4485b575cf9e5b3414b89b <32cd78c5610f02a929f63cac985e73692d05f33e
- Affected versionversion=14fceff4771e51b23b4485b575cf9e5b3414b89b <54d6802c4d83fa8de7696cfec06f475d5fd92d27
- Affected versionversion=14fceff4771e51b23b4485b575cf9e5b3414b89b <7c8df6fad43d9d5d77f281f794b2a93cd02fd1a9
- Affected versionversion=14fceff4771e51b23b4485b575cf9e5b3414b89b <c2ae49a113a5344232f1ebb93bcf18bbd11e9c39
- Affected versionversion=4.20
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
No sourced classifications are available.
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