CVE-2026-52941

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/smc: avoid NULL deref of conn->lnk in smc_msg_event tracepoint

The smc_msg_event tracepoint class, shared by smc_tx_sendmsg and smc_rx_recvmsg, unconditionally dereferences smc->conn.lnk:

__string(name, smc->conn.lnk->ibname)

conn->lnk is only set for SMC-R; for SMC-D it is NULL. Other code on these paths already handles this (e.g. !conn->lnk in SMC_STAT_RMB_TX_SIZE_SMALL()). With the tracepoint enabled, the first sendmsg()/recvmsg() on an SMC-D socket crashes:

Oops: general protection fault, probably for non-canonical address KASAN: null-ptr-deref in range [...] RIP: 0010:strlen+0x1e/0xa0 Call Trace: trace_event_raw_event_smc_msg_event (net/smc/smc_tracepoint.h:44) smc_rx_recvmsg (net/smc/smc_rx.c:515) smc_recvmsg (net/smc/af_smc.c:2859) __sys_recvfrom (net/socket.c:2315) __x64_sys_recvfrom (net/socket.c:2326) do_syscall_64

The faulting address 0x3e0 is offsetof(struct smc_link, ibname), confirming the NULL ->lnk deref. Enabling the tracepoint requires root, but the trigger itself is unprivileged: socket(AF_SMC, ...) has no capability check, and SMC-D negotiation needs no admin step on s390 or on x86 with the loopback ISM device loaded.

Log an empty device name for SMC-D instead of dereferencing NULL.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 8, 2026

Advisory Details (6)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

net/smc: avoid NULL deref of conn->lnk in smc_msg_event tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2ea0b8aef8746e147602eac87ca8538f4bc7e66
generic

net/smc: avoid NULL deref of conn->lnk in smc_msg_event tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b706d6d76a2a2793fe5ad0fbc2a75b6a460094ef
generic

net/smc: avoid NULL deref of conn->lnk in smc_msg_event tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bf563badd37cb796df5477d2b78bb64148a1268
generic

net/smc: avoid NULL deref of conn->lnk in smc_msg_event tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/720c76b930c52cd58f50eb6b10569d03dccc7959
generic

net/smc: avoid NULL deref of conn->lnk in smc_msg_event tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68200112534bb2acd1d7117dc2d5c124868d866d
generic

net/smc: avoid NULL deref of conn->lnk in smc_msg_event tracepoint - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/561cf66fa9b6c86dfe4e687d2d1aeaaa6739917f

Vendor Advisories for CVE-2026-52941(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 61× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 189 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:21 UTCEG score recompute
  11. 2026-08-30 20:21 UTCVendor advisory
  12. 2026-08-30 20:21 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-28 04:52 UTCEG score recompute
  16. 2026-08-28 04:52 UTCVendor advisory
  17. 2026-08-28 04:52 UTCGHSA enrichment
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 13:50 UTCEG score recompute
  22. 2026-08-24 13:50 UTCVendor advisory
  23. 2026-08-24 13:50 UTCGHSA enrichment
  24. 2026-08-23 11:21 UTCEG score recompute
  25. 2026-08-23 11:21 UTCVendor advisory
Show 75 more
  1. 2026-08-23 11:21 UTCGHSA enrichment
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-22 13:19 UTCEG score recompute
  4. 2026-08-22 13:19 UTCVendor advisory
  5. 2026-08-22 13:19 UTCGHSA enrichment
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 05:39 UTCEG score recompute
  8. 2026-08-21 05:39 UTCVendor advisory
  9. 2026-08-21 05:39 UTCGHSA enrichment
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 07:36 UTCEG score recompute
  12. 2026-08-20 07:36 UTCVendor advisory
  13. 2026-08-20 07:36 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 02:22 UTCEG score recompute
  16. 2026-08-19 02:22 UTCVendor advisory
  17. 2026-08-19 02:21 UTCGHSA enrichment
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-16 20:09 UTCEG score recompute
  20. 2026-08-16 20:09 UTCVendor advisory
  21. 2026-08-16 20:09 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 20:48 UTCEG score recompute
  25. 2026-08-15 20:48 UTCVendor advisory
  26. 2026-08-15 20:48 UTCGHSA enrichment
  27. 2026-08-15 01:30 UTCEPSS rescore
  28. 2026-08-14 22:14 UTCVendor advisory
  29. 2026-08-14 22:14 UTCGHSA enrichment
  30. 2026-08-14 00:12 UTCEG score recompute
  31. 2026-08-14 00:12 UTCVendor advisory
  32. 2026-08-14 00:12 UTCGHSA enrichment
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-13 02:10 UTCEG score recompute
  35. 2026-08-13 02:10 UTCVendor advisory
  36. 2026-08-13 02:10 UTCGHSA enrichment
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-12 04:08 UTCEG score recompute
  39. 2026-08-12 04:08 UTCVendor advisory
  40. 2026-08-12 04:08 UTCGHSA enrichment
  41. 2026-08-11 06:06 UTCEG score recompute
  42. 2026-08-11 06:06 UTCVendor advisory
  43. 2026-08-11 06:06 UTCGHSA enrichment
  44. 2026-08-11 00:00 UTCEPSS rescore
  45. 2026-08-10 08:04 UTCEG score recompute
  46. 2026-08-10 08:04 UTCVendor advisory
  47. 2026-08-10 08:03 UTCGHSA enrichment
  48. 2026-08-09 13:46 UTCEPSS rescore
  49. 2026-08-09 10:01 UTCEG score recompute
  50. 2026-08-09 10:01 UTCVendor advisory
  51. 2026-08-09 10:01 UTCGHSA enrichment
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 11:59 UTCEG score recompute
  54. 2026-08-08 11:59 UTCVendor advisory
  55. 2026-08-08 11:59 UTCGHSA enrichment
  56. 2026-08-07 13:56 UTCVendor advisory
  57. 2026-08-07 13:56 UTCGHSA enrichment
  58. 2026-08-06 15:54 UTCEG score recompute
  59. 2026-08-06 15:54 UTCVendor advisory
  60. 2026-08-06 15:54 UTCGHSA enrichment
  61. 2026-08-06 13:47 UTCEPSS rescore
  62. 2026-08-05 19:17 UTCEPSS rescore
  63. 2026-08-05 17:23 UTCVendor advisory
  64. 2026-08-05 17:23 UTCGHSA enrichment
  65. 2026-08-04 15:13 UTCEG score recompute
  66. 2026-08-04 15:13 UTCVendor advisory
  67. 2026-08-04 15:13 UTCGHSA enrichment
  68. 2026-08-04 15:10 UTCEPSS rescore
  69. 2026-08-04 10:39 UTCEPSS rescore
  70. 2026-08-03 16:46 UTCEG score recompute
  71. 2026-08-03 16:46 UTCVendor advisory
  72. 2026-08-03 16:46 UTCGHSA enrichment
  73. 2026-08-03 10:36 UTCEPSS rescore
  74. 2026-08-02 18:44 UTCEG score recompute
  75. 2026-08-02 18:44 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-52941?
CVE-2026-52941 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid NULL deref of conn->lnk in smcmsgevent tracepoint The smcmsgevent tracepoint class, shared by smctxsendmsg and smcrxrecvmsg, unconditionally dereferences smc->conn.lnk: string(name, smc->conn.lnk->ibname) conn->lnk…
When was CVE-2026-52941 disclosed?
CVE-2026-52941 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52941 actively exploited?
CVE-2026-52941 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-52941?
CVE-2026-52941 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52941?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52941, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52941

Explore →

Is Your Infrastructure Affected by CVE-2026-52941?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs