cbcvebase.
CVE-2024-41006
published 2024-07-12

CVE-2024-41006: In the Linux kernel, the following vulnerability has been resolved: netrom: Fix a memory leak in nr_heartbeat_expiry() syzbot reported a memory leak in…

PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.4th percentile
In the Linux kernel, the following vulnerability has been resolved: netrom: Fix a memory leak in nr_heartbeat_expiry() syzbot reported a memory leak in nr_create() [0]. Commit 409db27e3a2e ("netrom: Fix use-after-free of a listening socket.") added sock_hold() to the nr_heartbeat_expiry() function, where a) a socket has a SOCK_DESTROY flag or b) a listening socket has a SOCK_DEAD flag. But in the case "a," when the SOCK_DESTROY flag is set, the file descriptor has already been closed and the nr_release() function has been called. So it makes no sense to hold the reference count because no one will call another nr_destroy_socket() and put it as in the case "b." nr_connect nr_establish_data_link nr_start_heartbeat nr_release switch (nr->state) case NR_STATE_3 nr->state = NR_STATE_2 sock_set_flag(sk, SOCK_DESTROY); nr_rx_frame nr_process_rx_frame switch (nr->state) case NR_STATE_2 nr_state2_machine() nr_disconnect() nr_sk(sk)->state = NR_STATE_0 sock_set_flag(sk, SOCK_DEAD) nr_heartbeat_expiry switch (nr->state) case NR_STATE_0 if (sock_flag(sk, SOCK_DESTROY) || (sk->sk_state == TCP_LISTEN && sock_flag(sk, SOCK_DEAD))) sock_hold() // ( !!! ) nr_destroy_socket() To fix the memory leak, let's call sock_hold() only for a listening socket. Found by InfoTeCS on behalf of Linux Verification Center (linuxtesting.org) with Syzkaller. [0]: https://syzkaller.appspot.com/bug?extid=d327a1f3b12e1e206c16

Affected

38 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.99-1 (bookworm)linux 6.1.99-1 (bookworm)
debianlinux-6.1< linux 6.1.99-1 (bookworm)linux 6.1.99-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux>= 4.14.305 < 4.154.15
linuxlinux>= 4.19.272 < 4.19.3174.19.317
linuxlinux>= 409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 < b6ebe4fed73eedeb73f4540f8edc4871945474c8b6ebe4fed73eedeb73f4540f8edc4871945474c8
linuxlinux>= 409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 < d377f5a28332954b19e373d36823e59830ab1712d377f5a28332954b19e373d36823e59830ab1712
linuxlinux>= 409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 < 0b9130247f3b6a1122478471ff0e014ea96bb7350b9130247f3b6a1122478471ff0e014ea96bb735
linuxlinux>= 5.10.166 < 5.10.2215.10.221
linuxlinux>= 5.15.91 < 5.15.1625.15.162
linuxlinux>= 5.4.231 < 5.4.2795.4.279
linuxlinux>= 51e394c6f81adbfe7c34d15f58b3d4d44f144acf < a02fd5d775cf9787ee7698c797e20f2fa13d2e2ba02fd5d775cf9787ee7698c797e20f2fa13d2e2b
linuxlinux>= 6.1.9 < 6.1.966.1.96
linuxlinux>= 7de16d75b20ab13b75a7291f449a1b00090edfea < 5391f9db2cab5ef1cb411be1ab7dbec728078fba5391f9db2cab5ef1cb411be1ab7dbec728078fba
linuxlinux>= a31caf5779ace8fa98b0d454133808e082ee7a1b < d616876256b38ecf9a1a1c7d674192c5346bc69cd616876256b38ecf9a1a1c7d674192c5346bc69c
linuxlinux>= d2d3ab1b1de3302de2c85769121fd4f890e47ceb < 280cf1173726a7059b628c610c71050d5c0b6937280cf1173726a7059b628c610c71050d5c0b6937
linuxlinux>= fe9b9e621cebe6b7e83f7e954c70f8bb430520e5 < e07a9c2a850cdebf625e7a1b8171bd23a8554313e07a9c2a850cdebf625e7a1b8171bd23a8554313
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.221-15.10.221-1
linuxlinux_kernel>= 0 < 6.1.99-16.1.99-1
linuxlinux_kernel>= 0 < 6.9.7-16.9.7-1
linuxlinux_kernel>= 0 < 6.9.7-16.9.7-1
linuxlinux_kernel>= 0 < 5.4.0-195.2155.4.0-195.215
linuxlinux_kernel>= 0 < 5.15.0-121.1315.15.0-121.131

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.8HIGH
vendor_ubuntu7.8HIGH
vendor_debian5.5MEDIUM
vendor_msrc5.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.