{"id":"DEBIAN-CVE-2024-26615","details":"In the Linux kernel, the following vulnerability has been resolved:  net/smc: fix illegal rmb_desc access in SMC-D connection dump  A crash was found when dumping SMC-D connections. It can be reproduced by following steps:  - run nginx/wrk test:   smc_run nginx   smc_run wrk -t 16 -c 1000 -d \u003cduration\u003e -H 'Connection: Close' \u003cURL\u003e  - continuously dump SMC-D connections in parallel:   watch -n 1 'smcss -D'   BUG: kernel NULL pointer dereference, address: 0000000000000030  CPU: 2 PID: 7204 Comm: smcss Kdump: loaded Tainted: G\tE      6.7.0+ #55  RIP: 0010:__smc_diag_dump.constprop.0+0x5e5/0x620 [smc_diag]  Call Trace:   \u003cTASK\u003e   ? __die+0x24/0x70   ? page_fault_oops+0x66/0x150   ? exc_page_fault+0x69/0x140   ? asm_exc_page_fault+0x26/0x30   ? __smc_diag_dump.constprop.0+0x5e5/0x620 [smc_diag]   ? __kmalloc_node_track_caller+0x35d/0x430   ? __alloc_skb+0x77/0x170   smc_diag_dump_proto+0xd0/0xf0 [smc_diag]   smc_diag_dump+0x26/0x60 [smc_diag]   netlink_dump+0x19f/0x320   __netlink_dump_start+0x1dc/0x300   smc_diag_handler_dump+0x6a/0x80 [smc_diag]   ? __pfx_smc_diag_dump+0x10/0x10 [smc_diag]   sock_diag_rcv_msg+0x121/0x140   ? __pfx_sock_diag_rcv_msg+0x10/0x10   netlink_rcv_skb+0x5a/0x110   sock_diag_rcv+0x28/0x40   netlink_unicast+0x22a/0x330   netlink_sendmsg+0x1f8/0x420   __sock_sendmsg+0xb0/0xc0   ____sys_sendmsg+0x24e/0x300   ? copy_msghdr_from_user+0x62/0x80   ___sys_sendmsg+0x7c/0xd0   ? __do_fault+0x34/0x160   ? do_read_fault+0x5f/0x100   ? do_fault+0xb0/0x110   ? __handle_mm_fault+0x2b0/0x6c0   __sys_sendmsg+0x4d/0x80   do_syscall_64+0x69/0x180   entry_SYSCALL_64_after_hwframe+0x6e/0x76  It is possible that the connection is in process of being established when we dump it. Assumed that the connection has been registered in a link group by smc_conn_create() but the rmb_desc has not yet been initialized by smc_buf_create(), thus causing the illegal access to conn-\u003ermb_desc. So fix it by checking before dump.","modified":"2026-09-01T20:05:21.805616333Z","published":"2024-03-11T18:15:19.337Z","upstream":["CVE-2024-26615"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2024-26615"}],"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.76-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~bpo11+1"],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-26615.json"}},{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.15-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-26615.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.15-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-26615.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"}]}