Kernel livelock via sleepable tracing lock
Published Feb 26, 2025 · Updated May 11, 2026
Improper locking in affected Linux kernel builds allows local users to cause a livelock through a specific real-time tracing setup. In output_printk(), spin_lock_irqsave() acquires a lock from atomic context; on PREEMPT_RT, that lock becomes a sleepable rt-spinlock and triggers an invalid-context call trace. Reachability requires a PREEMPT_RT kernel booted with trace_event=initcall:initcall_start and tp_printk=1, and the reported consequence is an availability-impacting livelock.
Summary
What happened
Improper locking in affected Linux kernel builds allows local users to cause a livelock through a specific real-time tracing setup. In output_printk(), spin_lock_irqsave() acquires a lock from atomic context; on PREEMPT_RT, that lock becomes a sleepable rt-spinlock and triggers an invalid-context call trace. Reachability requires a PREEMPT_RT kernel booted with trace_event=initcall:initcall_start and tp_printk=1, and the reported consequence is an availability-impacting livelock.
The record
- CVE
- CVE-2022-49322
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- 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=0daa2302968c13b657118d6ac92471f8fd2f3f28 <12025abdc8539ed9d5014e2d647a3fd1bd3de5cd
- Affected versionversion=0daa2302968c13b657118d6ac92471f8fd2f3f28 <1788e6dbb61286215442b1af99e51405a6206762
- Affected versionversion=0daa2302968c13b657118d6ac92471f8fd2f3f28 <40f9fde06b25884baa0c4bd138b909a9b67218b4
- Affected versionversion=0daa2302968c13b657118d6ac92471f8fd2f3f28 <43bfc4dccc416c964b53cbdc430e814f8b6f770b
- Affected versionversion=0daa2302968c13b657118d6ac92471f8fd2f3f28 <48c6ee7d6c614f09b2c8553a95eefef6ecf196e0
- Affected versionversion=0daa2302968c13b657118d6ac92471f8fd2f3f28 <9abf3db8bdb63ab545034148ef2118f4d088ca59
- Affected versionversion=0daa2302968c13b657118d6ac92471f8fd2f3f28 <9b534640a2c6a8d88168febc82ec6d161184f2ec
- Affected versionversion=0daa2302968c13b657118d6ac92471f8fd2f3f28 <be1f323fb9d9b14a505ca22d742d321769454de1
- Affected versionversion=3.19
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