System hang via recursive tracing spinlock deadlock
Published Feb 27, 2024 · Updated May 11, 2026
Improper synchronization in Linux kernel tracing allows local users to hang an affected system during suspend or resume. When function-graph tracing recursively reenters ring_buffer_lock_reserve(), trace_clock_global() takes the same spin lock twice instead of avoiding a blocking update of prev_time. The path requires local low-privileged access and function-graph tracing during a power-management transition; the bounded consequence is a system deadlock.
Summary
What happened
Improper synchronization in Linux kernel tracing allows local users to hang an affected system during suspend or resume. When function-graph tracing recursively reenters ring_buffer_lock_reserve(), trace_clock_global() takes the same spin lock twice instead of avoiding a blocking update of prev_time. The path requires local low-privileged access and function-graph tracing during a power-management transition; the bounded consequence is a system deadlock.
The record
- CVE
- CVE-2021-46939
- Published
- Feb 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-662, CWE-400
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 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=14131f2f98ac350ee9e73faed916d2238a8b6a0d <1fca00920327be96f3318224f502e4d5460f9545
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <2a1bd74b8186d7938bf004f5603f25b84785f63e
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <6e2418576228eeb12e7ba82edb8f9500623942ff
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <859b47a43f5a0e5b9a92b621dc6ceaad39fb5c8b
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <91ca6f6a91f679c8645d7f3307e03ce86ad518c4
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <a33614d52e97fc8077eb0b292189ca7d964cc534
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <aafe104aa9096827a429bc1358f8260ee565b7cc
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <c64da3294a7d59a4bf6874c664c13be892f15f44
- Affected versionversion=14131f2f98ac350ee9e73faed916d2238a8b6a0d <d43d56dbf452ccecc1ec735cd4b6840118005d7c
- Affected versionversion=2.6.30
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