CVE-2026-63909 json
ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops
published 3mo ago modified 12d ago also EUVD-2026-45682
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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().
Patch / fix
- Linux Linux 6.6.143, 6.12.93, 6.18.35, 7.0.12
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.12-1
debian advisories DEBIAN-CVE-2026-63909
- linux Ubuntu 24.04 LTS 6.8.0-146.146
- linux Ubuntu 26.04 LTS 7.0.0-28.28
- linux-aws Ubuntu 24.04 LTS 6.8.0-1066.69
- linux-aws Ubuntu 26.04 LTS 7.0.0-1009.9
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1070.78
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gke Ubuntu 24.04 LTS 6.8.0-1065.73
- linux-gke Ubuntu 26.04 LTS 7.0.0-1003.4
ubuntu advisories UBUNTU-CVE-2026-63909
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/5500ba1d410aed1eded3eb04a76b10cfb4409334 commit
- git.kernel.org/stable/c/f6324b4240cf0b26a84c33f68a1222d727ff4af2 commit
- git.kernel.org/stable/c/0fe08c5776a798f46df1fd74b331be26bdd644d6 commit
- git.kernel.org/stable/c/d333af32e4451285e427f2d9c29de3a39f6f6d48 commit
- git.kernel.org/stable/c/94215d55b09445993929f4fc966061d61de74929 commit
- git.kernel.org/stable/c/4f7c131d2bdd7cd64b96f60d10be5ea72253f520 commit
- git.kernel.org/stable/c/0e60dafe97eca61721f3db456f97d97a80c6c8ae commit
Is CVE-2026-63909 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-63909 updated
kernel: ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/5500ba1d410aed1eded3eb04a76b10cfb4409334
patch
-
git.kernel.org
/stable/c/f6324b4240cf0b26a84c33f68a1222d727ff4af2
patch
-
git.kernel.org
/stable/c/0fe08c5776a798f46df1fd74b331be26bdd644d6
patch
-
git.kernel.org
/stable/c/d333af32e4451285e427f2d9c29de3a39f6f6d48
patch
-
git.kernel.org
/stable/c/94215d55b09445993929f4fc966061d61de74929
patch
-
git.kernel.org
/stable/c/4f7c131d2bdd7cd64b96f60d10be5ea72253f520
patch
-
git.kernel.org
/stable/c/0e60dafe97eca61721f3db456f97d97a80c6c8ae
patch
Sources
- CVE List CVE-2026-63909
- NVD CVE-2026-63909
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.