CVE-2022-49322
published 2025-02-26CVE-2022-49322: In the Linux kernel, the following vulnerability has been resolved: tracing: Fix sleeping function called from invalid context on RT kernel When setting…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
12.0th percentile
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix sleeping function called from invalid context on RT kernel
When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the
cmdline, the output_printk() was called, and the spin_lock_irqsave() was called in the
atomic and irq disable interrupt context suitation. On the PREEMPT_RT kernel,
these locks are replaced with sleepable rt-spinlock, so the stack calltrace will
be triggered.
Fix it by raw_spin_lock_irqsave when PREEMPT_RT and "trace_event=initcall:initcall_start
tp_printk=1" enabled.
BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0
preempt_count: 2, expected: 0
RCU nest depth: 0, expected: 0
Preemption disabled at:
[] try_to_wake_up+0x7e/0xba0
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.1-rt17+ #19 34c5812404187a875f32bee7977f7367f9679ea7
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
Call Trace:
dump_stack_lvl+0x60/0x8c
dump_stack+0x10/0x12
__might_resched.cold+0x11d/0x155
rt_spin_lock+0x40/0x70
trace_event_buffer_commit+0x2fa/0x4c0
? map_vsyscall+0x93/0x93
trace_event_raw_event_initcall_start+0xbe/0x110
? perf_trace_initcall_finish+0x210/0x210
? probe_sched_wakeup+0x34/0x40
? ttwu_do_wakeup+0xda/0x310
? trace_hardirqs_on+0x35/0x170
? map_vsyscall+0x93/0x93
do_one_initcall+0x217/0x3c0
? trace_event_raw_event_initcall_level+0x170/0x170
? push_cpu_stop+0x400/0x400
? cblist_init_generic+0x241/0x290
kernel_init_freeable+0x1ac/0x347
? _raw_spin_unlock_irq+0x65/0x80
? rest_init+0xf0/0xf0
kernel_init+0x1e/0x150
ret_from_fork+0x22/0x30
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < be1f323fb9d9b14a505ca22d742d321769454de1 | be1f323fb9d9b14a505ca22d742d321769454de1 |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < 40f9fde06b25884baa0c4bd138b909a9b67218b4 | 40f9fde06b25884baa0c4bd138b909a9b67218b4 |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < 48c6ee7d6c614f09b2c8553a95eefef6ecf196e0 | 48c6ee7d6c614f09b2c8553a95eefef6ecf196e0 |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < 1788e6dbb61286215442b1af99e51405a6206762 | 1788e6dbb61286215442b1af99e51405a6206762 |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < 9b534640a2c6a8d88168febc82ec6d161184f2ec | 9b534640a2c6a8d88168febc82ec6d161184f2ec |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < 43bfc4dccc416c964b53cbdc430e814f8b6f770b | 43bfc4dccc416c964b53cbdc430e814f8b6f770b |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < 9abf3db8bdb63ab545034148ef2118f4d088ca59 | 9abf3db8bdb63ab545034148ef2118f4d088ca59 |
| linux | linux | >= 0daa2302968c13b657118d6ac92471f8fd2f3f28 < 12025abdc8539ed9d5014e2d647a3fd1bd3de5cd | 12025abdc8539ed9d5014e2d647a3fd1bd3de5cd |
| linux | linux_kernel | < 4.14.283 | 4.14.283 |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 4.15 < 4.19.247 | 4.19.247 |
| linux | linux_kernel | >= 4.20 < 5.4.198 | 5.4.198 |
| linux | linux_kernel | >= 5.11 < 5.15.47 | 5.15.47 |
| linux | linux_kernel | >= 5.16 < 5.17.15 | 5.17.15 |
| linux | linux_kernel | >= 5.18 < 5.18.4 | 5.18.4 |
| linux | linux_kernel | >= 5.5 < 5.10.122 | 5.10.122 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-9cc8-5cmc-hcj3: In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix sleeping function called from invalid context on RT kernel
When set
ghsa_unreviewed·2025-04-14
CVE-2022-49322 [MEDIUM] CWE-667 GHSA-9cc8-5cmc-hcj3: In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix sleeping function called from invalid context on RT kernel
When set
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix sleeping function called from invalid context on RT kernel
When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the
cmdline, the output_printk() was called, and the spin_lock_irqsave() was called in the
atomic and irq disable interrupt context suitation. On the PREEMPT_RT kernel,
these locks are replaced with sleepable rt-spinlock, so the stack calltrace will
be triggered.
Fix it by raw_spin_lock_irqsave when PREEMPT_RT and "trace_event=initcall:initcall_start
tp_printk=1" enabled.
BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0
preempt_count: 2, expected: 0
RCU nest depth:
OSV
CVE-2022-49322: In the Linux kernel, the following vulnerability has been resolved: tracing: Fix sleeping function called from invalid context on RT kernel When setti
osv·2025-02-26·CVSS 5.5
CVE-2022-49322 [MEDIUM] CVE-2022-49322: In the Linux kernel, the following vulnerability has been resolved: tracing: Fix sleeping function called from invalid context on RT kernel When setti
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix sleeping function called from invalid context on RT kernel When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the cmdline, the output_printk() was called, and the spin_lock_irqsave() was called in the atomic and irq disable interrupt context suitation. On the PREEMPT_RT kernel, these locks are replaced with sleepable rt-spinlock, so the stack calltrace will be triggered. Fix it by raw_spin_lock_irqsave when PREEMPT_RT and "trace_event=initcall:initcall_start tp_printk=1" enabled. BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0 preempt_count: 2, expected: 0 RCU nest depth: 0,
Red Hat
kernel: tracing: Fix sleeping function called from invalid context on RT kernel
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49322 [MEDIUM] CWE-667 kernel: tracing: Fix sleeping function called from invalid context on RT kernel
kernel: tracing: Fix sleeping function called from invalid context on RT kernel
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix sleeping function called from invalid context on RT kernel
When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the
cmdline, the output_printk() was called, and the spin_lock_irqsave() was called in the
atomic and irq disable interrupt context suitation. On the PREEMPT_RT kernel,
these locks are replaced with sleepable rt-spinlock, so the stack calltrace will
be triggered.
Fix it by raw_spin_lock_irqsave when PREEMPT_RT and "trace_event=initcall:initcall_start
tp_printk=1" enabled.
BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46
in_atomic(): 1, irqs_disabled(): 0, non_b
Debian
CVE-2022-49322: linux - In the Linux kernel, the following vulnerability has been resolved: tracing: Fi...
vendor_debian·2022·CVSS 5.5
CVE-2022-49322 [MEDIUM] CVE-2022-49322: linux - In the Linux kernel, the following vulnerability has been resolved: tracing: Fi...
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix sleeping function called from invalid context on RT kernel When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the cmdline, the output_printk() was called, and the spin_lock_irqsave() was called in the atomic and irq disable interrupt context suitation. On the PREEMPT_RT kernel, these locks are replaced with sleepable rt-spinlock, so the stack calltrace will be triggered. Fix it by raw_spin_lock_irqsave when PREEMPT_RT and "trace_event=initcall:initcall_start tp_printk=1" enabled. BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0 preempt_count: 2, expected: 0 RCU nest depth: 0,
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/12025abdc8539ed9d5014e2d647a3fd1bd3de5cdhttps://git.kernel.org/stable/c/1788e6dbb61286215442b1af99e51405a6206762https://git.kernel.org/stable/c/40f9fde06b25884baa0c4bd138b909a9b67218b4https://git.kernel.org/stable/c/43bfc4dccc416c964b53cbdc430e814f8b6f770bhttps://git.kernel.org/stable/c/48c6ee7d6c614f09b2c8553a95eefef6ecf196e0https://git.kernel.org/stable/c/9abf3db8bdb63ab545034148ef2118f4d088ca59https://git.kernel.org/stable/c/9b534640a2c6a8d88168febc82ec6d161184f2echttps://git.kernel.org/stable/c/be1f323fb9d9b14a505ca22d742d321769454de1
2025-02-26
Published