CVE-2026-63909

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops

Commit d07b26f39246 ("ksmbd: require minimum ACE size in smb_check_perm_dacl()") introduced a transposed bounds check:

if (offsetof(struct smb_ace, sid) + aces_size < CIFS_SID_BASE_SIZE)

Since offsetof(..sid) is 8 and CIFS_SID_BASE_SIZE is 8, this evaluates to aces_size < 0. Because aces_size is always non-negative, this check becomes dead code and never breaks the loop.

Worse, that commit removed the old 4-byte guard, meaning the loop now reads ace->size (offset 2) even when aces_size is 0-3 bytes. This re-opens a 2-byte heap out-of-bounds (OOB) read past the pntsd allocation during subsequent SMB2_CREATE operations.

Fix this by properly transposing the comparison to require at least 16 bytes (8-byte offset + 8-byte SID base), matching the correct form used in smb_inherit_dacl().

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (7)

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

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94215d55b09445993929f4fc966061d61de74929
generic

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5500ba1d410aed1eded3eb04a76b10cfb4409334
generic

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f7c131d2bdd7cd64b96f60d10be5ea72253f520
generic

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e60dafe97eca61721f3db456f97d97a80c6c8ae

Vendor Advisories for CVE-2026-63909(1)

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

Patch Availability(4)

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

(2 across 2 ecosystems)
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 (138 versions)7.0.12-1

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 29× in last 7d / 153× 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 199 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63909?
CVE-2026-63909 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: OOB read regression in smbcheckperm_dacl() ACE-walk loops Commit d07b26f39246 ("ksmbd: require minimum ACE size in smbcheckperm_dacl()") introduced a transposed bounds check: if (offsetof(struct smbace, sid) + acessize <…
When was CVE-2026-63909 disclosed?
CVE-2026-63909 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63909 actively exploited?
CVE-2026-63909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63909?
CVE-2026-63909 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63909, 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-63909

Explore →

Is Your Infrastructure Affected by CVE-2026-63909?

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