CVE-2024-36286

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu() syzbot reported that nf_reinject() could be called without rcu_read_lock() : WARNING: suspicious RCU usage 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted net/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 2 locks held by syz-executor.4/13427: #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline] #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline] #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471 #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline] #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172 stack backtrace: CPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline] nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397 nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline] instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172 rcu_do_batch kernel/rcu/tree.c:2196 [inline] rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471 handle_softirqs+0x2d6/0x990 kernel/softirq.c:554 __do_softirq kernel/softirq.c:588 [inline] invoke_softirq kernel/softirq.c:428 [inline] __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637 irq_exit_rcu+0x9/0x30 kernel/softirq.c:649 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043 </IRQ> <TASK>

Gravité et risque d'exploitation

CVE-2024-36286 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.28 %, ce qui la place devant 18.9 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <8f365564af898819a523f1a8cf5c6ce053e9f718, <=6.1.*, 6.9.4, 6.10, 0, <25ea5377e3d2921a0f96ae2551f5ab1b36825dd4, <=5.10.*, <=6.6.*, <=6.9.*, 5.10.219, 9872bec773c2e8503fec480c1e8a0c732517e257, <dc21c6cc3d6986d938efbf95de62473982c98dec, <8658bd777cbfcb0c13df23d0ea120e70517761b9, 4.19.316, <=5.4.*, 6.6.33, <e01065b339e323b3dfa1be217fd89e9b3208b0ab, <=4.19.*, 5.4.278, 5.15.161, <3989b817857f4890fab9379221a9d3f52bf5c256, <68f40354a3851df46c27be96b84f11ae193e36c5, 2.6.25, <2.6.25, 6.1.93, <=*, <=5.15.*, <215df6490e208bfdd5b3012f5075e7f8736f3e7a) 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

• https://git.kernel.org/stable/c/8658bd777cbfcb0c13df23d0ea120e70517761b9
• https://git.kernel.org/stable/c/3989b817857f4890fab9379221a9d3f52bf5c256
• https://git.kernel.org/stable/c/e01065b339e323b3dfa1be217fd89e9b3208b0ab
• https://git.kernel.org/stable/c/25ea5377e3d2921a0f96ae2551f5ab1b36825dd4
• https://git.kernel.org/stable/c/68f40354a3851df46c27be96b84f11ae193e36c5
• https://git.kernel.org/stable/c/8f365564af898819a523f1a8cf5c6ce053e9f718
• https://git.kernel.org/stable/c/215df6490e208bfdd5b3012f5075e7f8736f3e7a
• https://git.kernel.org/stable/c/dc21c6cc3d6986d938efbf95de62473982c98dec