CVE-2024-41006

published 12 Jul 2024 · updated 17 Nov 2026

netrom: Fix a memory leak in nr_heartbeat_expiry()

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e07a9c2a850cdebf625e7a1b8171bd23a8554313, Kernel 5.10.221, Kernel 5.15.162 and 13 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=fe9b9e621cebe6b7e83f7e954c70f8bb430520e5 <e07a9c2a850cdebf625e7a1b8171bd23a8554313, >=5.10.166 <5.10.221, >=5.15.91 <5.15.162, >=5.4.231 <5.4.279, >=51e394c6f81adbfe7c34d15f58b3d4d44f144acf <a02fd5d775cf9787ee7698c797e20f2fa13d2e2b, >=6.1.9 <6.1.96, >=7de16d75b20ab13b75a7291f449a1b00090edfea <5391f9db2cab5ef1cb411be1ab7dbec728078fba, >=a31caf5779ace8fa98b0d454133808e082ee7a1b <d616876256b38ecf9a1a1c7d674192c5346bc69c, >=d2d3ab1b1de3302de2c85769121fd4f890e47ceb <280cf1173726a7059b628c610c71050d5c0b6937, =6.2, =e666990abb2e42dd4ba979b4706280a3664cfae7, >=4.14.305 <4.15, >=4.19.272 <4.19.317, >=409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 <0b9130247f3b6a1122478471ff0e014ea96bb735, >=409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 <b6ebe4fed73eedeb73f4540f8edc4871945474c8, >=409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 <d377f5a28332954b19e373d36823e59830ab1712e07a9c2a850cdebf625e7a1b8171bd23a8554313, 5.10.221, 5.15.162, 5.4.279, a02fd5d775cf9787ee7698c797e20f2fa13d2e2b, 6.1.96, 5391f9db2cab5ef1cb411be1ab7dbec728078fba, d616876256b38ecf9a1a1c7d674192c5346bc69c, 280cf1173726a7059b628c610c71050d5c0b6937, 4.15, 4.19.317, 0b9130247f3b6a1122478471ff0e014ea96bb735, b6ebe4fed73eedeb73f4540f8edc4871945474c8, d377f5a28332954b19e373d36823e59830ab1712
linux-kernel: Kernel>=4.19.272 <4.19.317, >=5.10.166 <5.10.221, >=5.15.91 <5.15.162, >=5.4.231 <5.4.279, >=6.1.9 <6.1.96, >=6.2.0 <6.6.36, >=6.7.0 <6.9.7, >=4.14.305 <4.154.19.317, 5.10.221, 5.15.162, 5.4.279, 6.1.96, 6.6.36, 6.9.7, 4.15

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-41006 severity on Zeptric[![CVE-2024-41006](https://zeptric.io/badge/cve/CVE-2024-41006.svg)](https://zeptric.io/cve/CVE-2024-41006)