Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 17 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63909, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Analyzed3.1High8.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.63% · top 49% of all CVEs (21 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.

Affected products

  • Linux · Linux

    • affected 282cbbb476b9f35793452bc461934af4c7eca169 – < 5500ba1d410aed1eded3eb04a76b10cfb4409334
    • affected f20adc4ef7428bc485ee83fd1a592252fb87718b – < f6324b4240cf0b26a84c33f68a1222d727ff4af2
    • affected 325d4ac11f526cb8964cff14548ccf02d8c756d8 – < 0fe08c5776a798f46df1fd74b331be26bdd644d6
    • affected 95e5aa3c3261da8c95b27d7aecf8ee39b9f86a4c – < d333af32e4451285e427f2d9c29de3a39f6f6d48
    • affected 90089584b2e25c4510b7b987387b4405f0673ece – < 94215d55b09445993929f4fc966061d61de74929
    • affected 151b1799861fde38087c08f613abc2843ef597b0 – < 4f7c131d2bdd7cd64b96f60d10be5ea72253f520
    • affected d07b26f39246a82399661936dd0c853983cfade7 – < 0e60dafe97eca61721f3db456f97d97a80c6c8ae
  • Linux · Linux

    • affected 6.6.140 – < 6.6.143
    • affected 6.12.84 – < 6.12.93
    • affected 6.18.25 – < 6.18.35
    • affected 7.0.2 – < 7.0.12

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63909 badge
[![CVE-2026-63909](https://cveledger.app/badge/CVE-2026-63909.svg)](https://cveledger.app/cve/CVE-2026-63909)

Record last updated .