CVE-2026-97555

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

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

smb: client: fix heap overflow in DACL owner/group rewrite

When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)).

If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation.

Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom.

KASAN reports this as: BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs] Write of size 4 at addr ffff8881a5e25374 by task chown/5298 ... The buggy address is located 0 bytes to the right of allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/100CISA SSVC

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
Severity88% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 3, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

smb: client: fix heap overflow in DACL owner/group rewrite - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ee150794c75bcd0be0e24ff3394f433cbae18cc
generic

smb: client: fix heap overflow in DACL owner/group rewrite - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a9aee9ef5622d58d8aafaa3263b3ffe70e2d9dd
generic

smb: client: fix heap overflow in DACL owner/group rewrite - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: fix heap overflow in DACL owner/group rewrite - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fb736ab4fb8c4fdb8b2f9ccd3a62e03d11549ca1

Vendor Advisories for CVE-2026-97555(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 41× in last 7d / 60× 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-10-05 01:58 UTCEG score recompute
  2. 2026-10-05 01:58 UTCVendor advisory
  3. 2026-10-05 01:58 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 13:08 UTCVendor advisory
  6. 2026-10-04 13:08 UTCGHSA enrichment
  7. 2026-10-04 00:18 UTCEG score recompute
  8. 2026-10-04 00:18 UTCVendor advisory
  9. 2026-10-04 00:18 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:29 UTCVendor advisory
  12. 2026-10-03 11:29 UTCGHSA enrichment
  13. 2026-10-03 04:53 UTCEG score recompute
  14. 2026-10-03 04:53 UTCVendor advisory
  15. 2026-10-03 04:53 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 16:02 UTCVendor advisory
  18. 2026-10-02 16:02 UTCGHSA enrichment
  19. 2026-10-02 03:12 UTCEG score recompute
  20. 2026-10-02 03:12 UTCVendor advisory
  21. 2026-10-02 03:12 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 14:22 UTCVendor advisory
  24. 2026-10-01 14:22 UTCGHSA enrichment
  25. 2026-10-01 01:32 UTCEG score recompute
Show 35 more
  1. 2026-10-01 01:32 UTCVendor advisory
  2. 2026-10-01 01:32 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 12:42 UTCVendor advisory
  5. 2026-09-30 12:42 UTCGHSA enrichment
  6. 2026-09-29 23:50 UTCEG score recompute
  7. 2026-09-29 23:50 UTCVendor advisory
  8. 2026-09-29 23:50 UTCGHSA enrichment
  9. 2026-09-29 09:21 UTCEG score recompute
  10. 2026-09-29 09:21 UTCVendor advisory
  11. 2026-09-29 09:21 UTCGHSA enrichment
  12. 2026-09-28 20:31 UTCEG score recompute
  13. 2026-09-28 20:31 UTCVendor advisory
  14. 2026-09-28 20:31 UTCGHSA enrichment
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-28 07:41 UTCVendor advisory
  18. 2026-09-28 07:41 UTCGHSA enrichment
  19. 2026-09-27 18:51 UTCEG score recompute
  20. 2026-09-27 18:51 UTCGHSA enrichment
  21. 2026-09-27 13:49 UTCEPSS rescore
  22. 2026-09-27 06:02 UTCGHSA enrichment
  23. 2026-09-26 17:12 UTCEG score recompute
  24. 2026-09-26 17:11 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
  26. 2026-09-26 04:17 UTCEG score recompute
  27. 2026-09-26 04:17 UTCGHSA enrichment
  28. 2026-09-25 15:26 UTCEG score recompute
  29. 2026-09-25 15:26 UTCGHSA enrichment
  30. 2026-09-25 14:53 UTCEG score recompute▲ 8.80
  31. 2026-09-25 14:52 UTCGHSA enrichment
  32. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  33. 2026-09-25 11:29 UTCNVD update
  34. 2026-09-25 10:40 UTCEG score recompute
  35. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97555?
CVE-2026-97555 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix heap overflow in DACL owner/group rewrite When idmodetocifsacl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by daclptr->size. However, replacesidsandcopy_aces…
When was CVE-2026-97555 disclosed?
CVE-2026-97555 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97555 actively exploited?
CVE-2026-97555 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97555?
CVE-2026-97555 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97555?
No fix for CVE-2026-97555 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97555 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-97555?

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