Skip to content
Fencer Vulns
medium 5.5

CVE-2024-26615 json

net/smc: fix illegal rmb_desc access in SMC-D connection dump

published 2024-02-29 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-23877

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 6.8
  • linux Debian 12 6.1.76-1
  • linux Debian 14, Debian 13 6.6.15-1

debian advisories DEBIAN-CVE-2024-26615

  • linux Ubuntu 20.04 LTS 5.4.0-181.201
  • linux Ubuntu 22.04 LTS 5.15.0-106.116
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1124.134
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1061.67
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1128.137
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1059.67
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1058.63
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1071.76

ubuntu advisories UBUNTU-CVE-2024-26615

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel RHEL 9 5.14.0-503.16.1.el9_5
  • rv RHEL 9 5.14.0-503.16.1.el9_5
  • perf RHEL 9 5.14.0-503.16.1.el9_5
  • rtla RHEL 9 5.14.0-503.16.1.el9_5
  • bpftool RHEL 9 7.4.0-503.16.1.el9_5
  • libperf RHEL 9 5.14.0-503.16.1.el9_5
  • kernel-rt RHEL 9 5.14.0-503.16.1.el9_5
  • kernel-64k RHEL 9 5.14.0-503.16.1.el9_5

red hat advisories RHSA-2024:10939RHSA-2024:10771RHSA-2024:3627RHSA-2024:3618

  • kernel-rt Linux Micro 6.0 6.4.0-9.1
  • kernel-source-rt Linux Micro 6.0 6.4.0-9.1
  • kernel-source Linux Micro 6.0 6.4.0-18.1
  • kernel-default Linux Micro 6.0 6.4.0-18.1
  • kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
  • kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
  • kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1
  • kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1

suse advisories SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1SUSE-SU-2024:2973-1SUSE-SU-2024:2947-1SUSE-SU-2024:2940-1SUSE-SU-2024:2939-1

  • kernel AlmaLinux 9 5.14.0-503.16.1.el9_5
  • rv AlmaLinux 9 5.14.0-503.16.1.el9_5
  • perf AlmaLinux 9 5.14.0-503.16.1.el9_5
  • rtla AlmaLinux 9 5.14.0-503.16.1.el9_5
  • bpftool AlmaLinux 9 7.4.0-503.16.1.el9_5
  • libperf AlmaLinux 9 5.14.0-503.16.1.el9_5
  • kernel-rt AlmaLinux 9 5.14.0-503.16.1.el9_5
  • kernel-64k AlmaLinux 9 5.14.0-503.16.1.el9_5

almalinux advisories ALSA-2024:10939ALSA-2024:3618ALSA-2024:3627

  • kernel-rt Rocky Linux 8 4.18.0-553.5.1.rt7.346.el8_10
  • kernel Rocky Linux 8 4.18.0-553.5.1.el8_10

rocky linux advisories RLSA-2024:3627RLSA-2024:3618

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-26615 updated cvss 5.5

kernel: net/smc: fix illegal rmb_desc access in SMC-D connection dump

  • Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +12 more
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat CodeReady Linux Builder (v. 9) libperf 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-s390x 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-x86_64 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-aarch64 5.14.0-503.16.1.el9_5, kernel-debuginfo-common-ppc64le 5.14.0-503.16.1.el9_5
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10939
  • Red Hat CodeReady Linux Builder EUS (v.9.4) libperf 5.14.0-427.47.1.el9_4, kernel-debuginfo-common-s390x 5.14.0-427.47.1.el9_4, kernel-debuginfo-common-x86_64 5.14.0-427.47.1.el9_4, kernel-debuginfo-common-aarch64 5.14.0-427.47.1.el9_4, kernel-debuginfo-common-ppc64le 5.14.0-427.47.1.el9_4
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10771
  • Red Hat Enterprise Linux AppStream (v. 9) rv 5.14.0-503.16.1.el9_5, perf 5.14.0-503.16.1.el9_5, rtla 5.14.0-503.16.1.el9_5, kernel-devel-matched 5.14.0-503.16.1.el9_5, kernel-64k-devel-matched 5.14.0-503.16.1.el9_5, kernel-debug-devel-matched 5.14.0-503.16.1.el9_5, +6 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10939
  • Red Hat Enterprise Linux AppStream EUS (v.9.4) rv 5.14.0-427.47.1.el9_4, perf 5.14.0-427.47.1.el9_4, rtla 5.14.0-427.47.1.el9_4, kernel-devel-matched 5.14.0-427.47.1.el9_4, kernel-64k-devel-matched 5.14.0-427.47.1.el9_4, kernel-debug-devel-matched 5.14.0-427.47.1.el9_4, +6 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10771
  • Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-553.5.1.el8_10, kernel 4.18.0-553.5.1.el8_10, bpftool 4.18.0-553.5.1.el8_10, kernel-core 4.18.0-553.5.1.el8_10, kernel-tools 4.18.0-553.5.1.el8_10, python3-perf 4.18.0-553.5.1.el8_10, +15 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3618
  • Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.4.0-503.16.1.el9_5, kernel 5.14.0-503.16.1.el9_5, kernel-64k 5.14.0-503.16.1.el9_5, kernel-core 5.14.0-503.16.1.el9_5, kernel-tools 5.14.0-503.16.1.el9_5, python3-perf 5.14.0-503.16.1.el9_5, +29 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10939
  • Red Hat Enterprise Linux BaseOS EUS (v.9.4) bpftool 7.3.0-427.47.1.el9_4, kernel 5.14.0-427.47.1.el9_4, kernel-64k 5.14.0-427.47.1.el9_4, kernel-core 5.14.0-427.47.1.el9_4, kernel-tools 5.14.0-427.47.1.el9_4, python3-perf 5.14.0-427.47.1.el9_4, +28 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10771
show 8 more
  • Red Hat Enterprise Linux CRB (v. 8) kernel-debuginfo-common-x86_64 4.18.0-553.5.1.el8_10, kernel-debuginfo-common-aarch64 4.18.0-553.5.1.el8_10, kernel-debuginfo-common-ppc64le 4.18.0-553.5.1.el8_10
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3618
  • Red Hat Enterprise Linux NFV (v. 8) kernel-rt 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-kvm 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-core 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-modules 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-debug-kvm 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-debug-core 4.18.0-553.5.1.rt7.346.el8_10, +4 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3627
  • Red Hat Enterprise Linux Real Time (v. 9) kernel-rt 5.14.0-503.16.1.el9_5, kernel-rt-core 5.14.0-503.16.1.el9_5, kernel-rt-modules 5.14.0-503.16.1.el9_5, kernel-rt-debug-core 5.14.0-503.16.1.el9_5, kernel-rt-modules-core 5.14.0-503.16.1.el9_5, kernel-rt-debug-modules 5.14.0-503.16.1.el9_5, +4 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10939
  • Red Hat Enterprise Linux Real Time EUS (v.9.4) kernel-rt 5.14.0-427.47.1.el9_4, kernel-rt-core 5.14.0-427.47.1.el9_4, kernel-rt-modules 5.14.0-427.47.1.el9_4, kernel-rt-debug-core 5.14.0-427.47.1.el9_4, kernel-rt-modules-core 5.14.0-427.47.1.el9_4, kernel-rt-debug-modules 5.14.0-427.47.1.el9_4, +4 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10771
  • Red Hat Enterprise Linux Real Time for NFV (v. 9) kernel-rt 5.14.0-503.16.1.el9_5, kernel-rt-kvm 5.14.0-503.16.1.el9_5, kernel-rt-core 5.14.0-503.16.1.el9_5, kernel-rt-modules 5.14.0-503.16.1.el9_5, kernel-rt-debug-kvm 5.14.0-503.16.1.el9_5, kernel-rt-debug-core 5.14.0-503.16.1.el9_5, +6 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10939
  • Red Hat Enterprise Linux Real Time for NFV EUS (v.9.4) kernel-rt 5.14.0-427.47.1.el9_4, kernel-rt-kvm 5.14.0-427.47.1.el9_4, kernel-rt-core 5.14.0-427.47.1.el9_4, kernel-rt-modules 5.14.0-427.47.1.el9_4, kernel-rt-debug-kvm 5.14.0-427.47.1.el9_4, kernel-rt-debug-core 5.14.0-427.47.1.el9_4, +6 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:10771
  • Red Hat Enterprise Linux RT (v. 8) kernel-rt 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-core 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-modules 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-debug-core 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-debug-modules 4.18.0-553.5.1.rt7.346.el8_10, kernel-rt-modules-extra 4.18.0-553.5.1.rt7.346.el8_10, +2 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3627
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

cisa ICSA-25-226-15 updated

Siemens SINEC OS

  • Siemens RUGGEDCOM RST2428P (6GK6242-6PA00) Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family
    not affected

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.