Heimdall Security Logo

CVE-2022-49322

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : <=5.17.*, 3.19, <1788e6dbb61286215442b1af99e51405a6206762, 0, 5.19, <be1f323fb9d9b14a505ca22d742d321769454de1, <48c6ee7d6c614f09b2c8553a95eefef6ecf196e0, <40f9fde06b25884baa0c4bd138b909a9b67218b4, 5.18.4, <=5.10.*, <=4.14.*, 5.15.47, 4.19.247, 5.4.198, <9abf3db8bdb63ab545034148ef2118f4d088ca59, <=5.18.*, <=5.4.*, 4.14.283, <=4.19.*, 5.10.122, 0daa2302968c13b657118d6ac92471f8fd2f3f28, <12025abdc8539ed9d5014e2d647a3fd1bd3de5cd, <9b534640a2c6a8d88168febc82ec6d161184f2ec, <=*, <43bfc4dccc416c964b53cbdc430e814f8b6f770b, <=5.15.*, <3.19, 5.17.15

Description

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: [<ffffffff8992303e>] 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: <TASK> 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 </TASK>

Gravité et risque d'exploitation

CVE-2022-49322 obtient un score CVSS de 5.5/10, soit une gravité moyenne. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 11.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=5.17.*, 3.19, <1788e6dbb61286215442b1af99e51405a6206762, 0, 5.19, <be1f323fb9d9b14a505ca22d742d321769454de1, <48c6ee7d6c614f09b2c8553a95eefef6ecf196e0, <40f9fde06b25884baa0c4bd138b909a9b67218b4, 5.18.4, <=5.10.*, <=4.14.*, 5.15.47, 4.19.247, 5.4.198, <9abf3db8bdb63ab545034148ef2118f4d088ca59, <=5.18.*, <=5.4.*, 4.14.283, <=4.19.*, 5.10.122, 0daa2302968c13b657118d6ac92471f8fd2f3f28, <12025abdc8539ed9d5014e2d647a3fd1bd3de5cd, <9b534640a2c6a8d88168febc82ec6d161184f2ec, <=*, <43bfc4dccc416c964b53cbdc430e814f8b6f770b, <=5.15.*, <3.19, 5.17.15) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE