System crash via NCI teardown timer race
Published Feb 26, 2025 · Updated May 11, 2026
Use-after-free in the Linux kernel NCI subsystem before 5.18 allows local users to crash the system while detaching an NCI device. During nci_unregister_device, cleanup deletes cmd_timer and frees ndev without first draining cmd_work, allowing nci_cmd_work to rearm the timer against freed memory. Triggering the demonstrated race requires physical access or CAP_SYS_ADMIN-equivalent privilege; the published proof demonstrates a kernel crash.
Summary
What happened
Use-after-free in the Linux kernel NCI subsystem before 5.18 allows local users to crash the system while detaching an NCI device. During nci_unregister_device, cleanup deletes cmd_timer and frees ndev without first draining cmd_work, allowing nci_cmd_work to rearm the timer against freed memory. Triggering the demonstrated race requires physical access or CAP_SYS_ADMIN-equivalent privilege; the published proof demonstrates a kernel crash.
The record
- CVE
- CVE-2022-49059
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499.004
- 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=3.2
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <1a1748d0dd0f0a98535c6baeef671c8722107639
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <5c63ad2b0a267a524c12c88acb1ba9c2d109a801
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <67677050cecbe0edfdd81cd508415e9636ba7c65
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <7d3232214ca4ea8f7d18df264c3b254aa8089d7f
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <9d243aff5f7e6b04e907c617426bbdf26e996ac8
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <9ded5ae40f4fe37fcc28f36d76bf45df20be5432
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <edd4600120641e1714e30112e69a548cfb68e067
- Affected versionversion=6a2968aaf50c7a22fced77a5e24aa636281efca8 <ef27324e2cb7bb24542d6cb2571740eefe6b00dc
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.
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