Local availability loss via device-node refcount leak
Published Feb 26, 2025 · Updated May 11, 2026
Resource leak in affected Linux kernel branches allows local users to cause availability loss on Xtensa systems during CPU setup. During CPU-counter calibration in arch/xtensa/kernel/time.c, calibrate_ccount obtains a refcounted device-tree node through of_find_compatible_node but does not release it with of_node_put after use. The path requires an Xtensa kernel built with device-tree CPU-clock calibration and runs during boot; no network reachability or data impact is reported.
Summary
What happened
Resource leak in affected Linux kernel branches allows local users to cause availability loss on Xtensa systems during CPU setup. During CPU-counter calibration in arch/xtensa/kernel/time.c, calibrate_ccount obtains a refcounted device-tree node through of_find_compatible_node but does not release it with of_node_put after use. The path requires an Xtensa kernel built with device-tree CPU-clock calibration and runs during boot; no network reachability or data impact is reported.
The record
- CVE
- CVE-2022-49682
- 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=205ad548a7426fb6813760cd9917d3fc24122576 <0dcc1dd8a5dd9240639f1051dfaa2dffc9fbbde5
- Affected versionversion=205ad548a7426fb6813760cd9917d3fc24122576 <0e403a383c14b63c86bd9df085b7e573e9caee64
- Affected versionversion=205ad548a7426fb6813760cd9917d3fc24122576 <3e5eb904d9ba657308fc75a5de434b0e58dcb8d7
- Affected versionversion=205ad548a7426fb6813760cd9917d3fc24122576 <7de4502af68f4f3932f450157f5483eb7b33cb74
- Affected versionversion=205ad548a7426fb6813760cd9917d3fc24122576 <a0117dc956429f2ede17b323046e1968d1849150
- Affected versionversion=205ad548a7426fb6813760cd9917d3fc24122576 <af0ff2da01521144bc11194f4c26485d7c9cee73
- Affected versionversion=205ad548a7426fb6813760cd9917d3fc24122576 <e5234a9d64a976abd134a14710dcd5188158a7c5
- Affected versionversion=205ad548a7426fb6813760cd9917d3fc24122576 <f1eaf4ba5372ad111f687a80c67e270708e14c23
- Affected versionversion=4.9
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
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