CVE-2026-52967

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

smb/client: fix possible infinite loop and oob read in symlink_data()

On 32-bit architectures, the infinite loop is as follows:

len = p->ErrorDataLength == 0xfffffff8 u8 *next = p->ErrorContextData + len next == p

On 32-bit architectures, the out-of-bounds read is as follows:

len = p->ErrorDataLength == 0xfffffff0 u8 *next = p->ErrorContextData + len next == (u8 *)p - 8

CVSS v3
8.1
EG Score
8.1(high)
EPSS
31.8%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (6)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

smb/client: fix possible infinite loop and oob read in symlink_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb/client: fix possible infinite loop and oob read in symlink_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb/client: fix possible infinite loop and oob read in symlink_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97a05b0ae9ea5ec052be2eef0f9cc7ce03501bbb
generic

smb/client: fix possible infinite loop and oob read in symlink_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb/client: fix possible infinite loop and oob read in symlink_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1cfa2d59f669db28d6292d10ff87ca6837c781b0
generic

smb/client: fix possible infinite loop and oob read in symlink_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b9331b16b0ed9414dcf7583d8134bdfeb117aae

Vendor Advisories for CVE-2026-52967(2)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 47× 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.

  1. 2026-07-06 22:46 UTCEG score recompute
  2. 2026-07-06 22:46 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 09:50 UTCEG score recompute
  6. 2026-07-06 09:50 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 20:53 UTCEG score recompute
  10. 2026-07-05 20:53 UTCGHSA enrichment
  11. 2026-07-05 07:53 UTCEG score recompute
  12. 2026-07-05 07:53 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 18:57 UTCEG score recompute
  16. 2026-07-04 18:57 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:00 UTCEG score recompute
  19. 2026-07-04 06:00 UTCGHSA enrichment
  20. 2026-07-03 17:04 UTCEG score recompute
  21. 2026-07-03 17:04 UTCGHSA enrichment
  22. 2026-07-03 04:07 UTCEG score recompute
  23. 2026-07-03 04:07 UTCGHSA enrichment
  24. 2026-07-02 15:10 UTCEG score recompute
  25. 2026-07-02 15:10 UTCGHSA enrichment
Show 22 more
  1. 2026-07-02 02:13 UTCEG score recompute
  2. 2026-07-02 02:13 UTCGHSA enrichment
  3. 2026-07-01 15:07 UTCEPSS rescore
  4. 2026-07-01 13:17 UTCEG score recompute
  5. 2026-07-01 13:17 UTCGHSA enrichment
  6. 2026-07-01 00:19 UTCEG score recompute
  7. 2026-07-01 00:19 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 11:22 UTCEG score recompute 8.10
  10. 2026-06-30 11:21 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 14:54 UTCEG score recompute
  18. 2026-06-27 14:54 UTCGHSA enrichment
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 18:28 UTCEG score recompute
  22. 2026-06-24 18:02 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-52967?
CVE-2026-52967 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: smb/client: fix possible infinite loop and oob read in symlink_data() On 32-bit architectures, the infinite loop is as follows: len = p->ErrorDataLength == 0xfffffff8 u8 *next = p->ErrorContextData + len next == p On 32-bit…
When was CVE-2026-52967 disclosed?
CVE-2026-52967 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52967 actively exploited?
CVE-2026-52967 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-52967?
CVE-2026-52967 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-52967?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52967, 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

Explore the affected products and dependency analysis for CVE-2026-52967

Explore →

Is Your Infrastructure Affected by CVE-2026-52967?

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