{"id":"DEBIAN-CVE-2024-41006","details":"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-\u003estate)   case NR_STATE_3     nr-\u003estate = NR_STATE_2     sock_set_flag(sk, SOCK_DESTROY);                          nr_rx_frame                           nr_process_rx_frame                             switch (nr-\u003estate)                             case NR_STATE_2                               nr_state2_machine()                                 nr_disconnect()                                   nr_sk(sk)-\u003estate = NR_STATE_0                                   sock_set_flag(sk, SOCK_DEAD)                          nr_heartbeat_expiry                           switch (nr-\u003estate)                           case NR_STATE_0                             if (sock_flag(sk, SOCK_DESTROY) ||                                (sk-\u003esk_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","modified":"2026-09-15T09:03:09.546723977Z","published":"2024-07-12T13:15:21.370Z","upstream":["CVE-2024-41006"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2024-41006"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:12","purl":"pkg:deb/debian/linux?arch=source&distro=bookworm"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.99-1"}]}],"versions":["6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1"],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-41006.json"}},{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.7-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-41006.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.9.7-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-41006.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}