CVE-2024-26615: Linux kernel · net/smc: fix illegal
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1124.134~18.04.1 : update Linux kernel when convenient.
Data as of 12 Nov 2026, 18:50 UTC
- Patch
- Available – fixed in 5.4.0-1124.134~18.04.1, 5.4.0-1129.136~18.04.1, 5.4.0-1128.137~18.04.1 +61
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6766-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6767-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6767-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6766-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6766-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6795-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6818-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6819-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6818-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6828-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6819-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6819-3 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro Realtime 24.04 LTSlinux-raspi-realtimepkg:deb/ubuntu/linux-raspi-realtime?arch=source&distro=realtime/nobleOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-allwinner-5.19pkg:deb/ubuntu/linux-allwinner-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-aws-5.19pkg:deb/ubuntu/linux-aws-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-aws-6.2pkg:deb/ubuntu/linux-aws-6.2?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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 <duration> -H 'Connection: Close' <URL> - 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 E 6.7.0+ #55 RIP: 0010:__smc_diag_dump.constprop.0+0x5e5/0x620 [smc_diag] Call Trace: <TASK> ? __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->rmb_desc. So fix it by checking before dump.
References
- ubuntu.com/security/CVE-2024-26615 (opens in a new tab)
- git.kernel.org/linus/dbc153fd3c142909e564bb256da087e13fbf239c (opens in a new tab)
- git.kernel.org/stable/c/27aea64838914c6122db5b8bd4bed865c9736f22 (opens in a new tab)
- git.kernel.org/stable/c/1fea9969b81c67d0cb1611d1b8b7d19049d937be (opens in a new tab)
- git.kernel.org/stable/c/5fed92ca32eafbfae8b6bee8ca34cca71c6a8b6d (opens in a new tab)
- git.kernel.org/stable/c/68b888d51ac82f2b96bf5e077a31d76afcdef25a (opens in a new tab)
- git.kernel.org/stable/c/6994dba06321e3c48fdad0ba796a063d9d82183a (opens in a new tab)
- git.kernel.org/stable/c/a164c2922675d7051805cdaf2b07daffe44f20d9 (opens in a new tab)
- git.kernel.org/stable/c/8f3f9186e5bb96a9c9654c41653210e3ea7e48a6 (opens in a new tab)
- git.kernel.org/stable/c/dbc153fd3c142909e564bb256da087e13fbf239c (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-26615 (opens in a new tab)
- ubuntu.com/security/notices/USN-6766-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6767-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6767-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6766-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6766-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6795-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6818-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6819-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6818-2 (opens in a new tab)