Answer in brief
CVE-2024-41006 records a Unknown severity vulnerability in netrom: Fix a memory leak in nr_heartbeat_expiry(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a31caf5779ace8fa98b0d454133808e082ee7a1b <d616876256b38ecf9a1a1c7d674192c5346bc69c || >=fe9b9e621cebe6b7e83f7e954c70f8bb430520e5 <e07a9c2a850cdebf625e7a1b8171bd23a8554313 || >=7de16d75b20ab13b75a7291f449a1b00090edfea <5391f9db2cab5ef1cb411be1ab7dbec728078fba || >=d2d3ab1b1de3302de2c85769121fd4f890e47ceb <280cf1173726a7059b628c610c71050d5c0b6937 || >=51e394c6f81adbfe7c34d15f58b3d4d44f144acf <a02fd5d775cf9787ee7698c797e20f2fa13d2e2b || >=409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 <b6ebe4fed73eedeb73f4540f8edc4871945474c8 || >=409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 <d377f5a28332954b19e373d36823e59830ab1712 || >=409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 <0b9130247f3b6a1122478471ff0e014ea96bb735 || e666990abb2e42dd4ba979b4706280a3664cfae7 || >=4.19.272 <4.19.317 || >=5.4.231 <5.4.279 || >=5.10.166 <5.10.221 || >=5.15.91 <5.15.162 || >=6.1.9 <6.1.96 || >=4.14.305 <4.15 | d616876256b38ecf9a1a1c7d674192c5346bc69c, e07a9c2a850cdebf625e7a1b8171bd23a8554313, 5391f9db2cab5ef1cb411be1ab7dbec728078fba, 280cf1173726a7059b628c610c71050d5c0b6937, a02fd5d775cf9787ee7698c797e20f2fa13d2e2b, b6ebe4fed73eedeb73f4540f8edc4871945474c8, d377f5a28332954b19e373d36823e59830ab1712, 0b9130247f3b6a1122478471ff0e014ea96bb735, 4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.96, 4.15 |
| Linux/Linuxgeneric | 6.2 | Not reported |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.1 | V3.1 |
| Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric | >=0 <V3.1 | V3.1 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <V1.1.1 | V1.1.1 |
Published upstream
Jul 12, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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
Quoted source text, attributed separately from HOL analysis.