Back to CVE records
Medium 5.5Published Jul 12, 2024

CVE-2024-41006netrom: Fix a memory leak in nr_heartbeat_expiry()

Updated under an hour ago ()

Does this affect you?

It affects Linux and 5 other products. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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

CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Modified
Record last updated
Oct 15, 2026
First seen by InfoSec Signals
Oct 15, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from a31caf5779ace8fa98b0d454133808e082ee7a1b before d616876256b38ecf9a1a1c7d674192c5346bc69c; from fe9b9e621cebe6b7e83f7e954c70f8bb430520e5 before e07a9c2a850cdebf625e7a1b8171bd23a8554313; from 7de16d75b20ab13b75a7291f449a1b00090edfea before 5391f9db2cab5ef1cb411be1ab7dbec728078fba; from d2d3ab1b1de3302de2c85769121fd4f890e47ceb before 280cf1173726a7059b628c610c71050d5c0b6937; from 51e394c6f81adbfe7c34d15f58b3d4d44f144acf before a02fd5d775cf9787ee7698c797e20f2fa13d2e2b; from 409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 before b6ebe4fed73eedeb73f4540f8edc4871945474c8; from 409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 before d377f5a28332954b19e373d36823e59830ab1712; 409db27e3a2eb5e8ef7226ca33be33361b3ed1c9 builds before 0b9130247f3b6a1122478471ff0e014ea96bb735; and 7 more ranges
CNA record
Siemens RUGGEDCOM RST2428P
siemens:ruggedcom_rst2428p (from the name)
before V3.1
CISA ADP
Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
siemens:scalance_xc_300_xr_300_xc_400_xr_500wg_xr_500_family (from the name)
all versions not affected
CISA ADP
Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family
siemens:scalance_xcm_xrm_xch_xrh_300_family (from the name)
before V3.1
CISA ADP
Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
siemens:simatic_s7_1500_tm_mfp_gnu_linux_subsystem (from the name)
before V1.1.1
CISA ADP
linux linux_kernel
linux:linux_kernel
from 4.19.272 before 4.19.317; from 5.4.231 before 5.4.279; from 5.10.166 before 5.10.221; from 5.15.91 before 5.15.162; from 6.1.9 before 6.1.96; from 6.2 before 6.6.36; from 6.7 before 6.9.7; 6.10; and 3 more ranges
NVD

References

  • mailing-list, patch
  • mailing-list, patch
  • mailing-list, patch
  • mailing-list, patch
  • mailing-list, patch
  • mailing-list, patch
  • mailing-list, patch
  • mailing-list, patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.