Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99309

ksmbd: fix overflow in dacloffset bounds check in build_sec_desc()

No exploitation reported by the sources we read.

  • Published2026-11-16
  • Fixed in7.3.2 · 6.18.61 · 6.12.117 · 5.20 · 5.19 · 5.16

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix overflow in dacloffset bounds check in build_sec_desc() When the large dacl_offset is provided, dacl_offset + sizeof(struct smb_acl) overflows on 32-bit builds and the check is passed, Which makes le16_to_cpu(ppdacl_ptr->size) read out-of-bounds. This only happens for dacl_offset in range [0xFFFFFFF8, 0xFFFFFFFF]. So the oob read is max 8 bytes preceding the allocated ppntsd. unsigned int dacl_offset = le32_to_cpu(ppntsd->dacloffset); int ppdacl_size, ntacl_size = ppntsd_size - dacl_offset; if (!dacl_offset || (dacl_offset + sizeof(struct smb_acl) > ppntsd_size)) goto out; Commit beff0bc9d69b ("ksmbd: fix overflow in dacloffset bounds check") fixes similar checks in other functions. But leaves this one out, because it is only valid for 32-bit builds. Reproduced on 32-bit ARM with KASAN, by a client sending SMB2 SET_INFO(SEC) with dacloffset=0xfffffff8, then QUERY_INFO(SEC) on the same file: BUG: KASAN: slab-out-of-bounds in build_sec_desc (fs/smb/server/smbacl.c:1105) Read of size 2 at addr c2a273fa by task kworker/1:1/35 CPU: 1 UID: 0 PID: 35 Comm: kworker/1:1 Not tainted 7.3.0-rc2+ #5 Workqueue: ksmbd-io handle_ksmbd_work Call trace: kasan_check_range from build_sec_desc (fs/smb/server/smbacl.c:1105) build_sec_desc from smb2_query_info (fs/smb/server/smb2pdu.c:7676) smb2_query_info from handle_ksmbd_work (fs/smb/server/server.c:160) handle_ksmbd_work from process_one_work (kernel/workqueue.c:3401) process_one_work from worker_thread (kernel/workqueue.c:3473) worker_thread from kthread (kernel/kthread.c:436) Add overflow check.

Timeline

dates in UTC
  1. 2026-11-1609:59CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.27.3.2
6.x≥ 6.13.0, < 6.18.616.18.61
6.x≥ 6.0.0, < 6.12.1176.12.117
5.x≥ 5.19.2, < 5.205.20
5.x≥ 5.18.18, < 5.195.19
5.x≥ 5.15.62, < 5.165.16

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < bd92e03122f33c159b552867a4abc098d405dfedfixed in bd92e03122f33c159b552867a4abc098d405dfedgit
    • ≥ 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < 4f238380ea3803afdc815c615521c6f6b13989a3fixed in 4f238380ea3803afdc815c615521c6f6b13989a3git
    • ≥ 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < d1e92aa651caa352261fb3b78460b7722357835cfixed in d1e92aa651caa352261fb3b78460b7722357835cgit
    • ≥ 8f0541186e9ad1b62accc9519cc2b7a7240272a7, < eb96e2a0e817807c48dc8387ca6a5249fdeae3a0fixed in eb96e2a0e817807c48dc8387ca6a5249fdeae3a0git
    • = cb69d4d6f709f87c94afa28ae64c501576692171no fix statedgit
    • = 6e8f4abf584253cbaa596ea4ad13110cf61cd4c9no fix statedgit
    • = 8e33102309bd6839b2e2e158f93a7b378cb4655dno fix statedgit
    • ≥ 5.15.62, < 5.16fixed in 5.16semver

    2 more version lines in the CVE record.

  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.0no fix stated

    Not affected < 6.0 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-16

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • kernelAzure Linux:3all versions · no fixed version listed
  • linuxUbuntu:26.10all versions · no fixed version listedand 8 other packages
  • linuxUbuntu:26.04:LTSall versions · no fixed version listedand 14 other packages
  • linuxUbuntu:24.04:LTSall versions · no fixed version listedand 52 other packages
  • linuxUbuntu:22.04:LTSall versions · no fixed version listedand 59 other packages
  • linuxDebian:14all versions · fixed in 7.3.3-1
  • linuxDebian:13all versions · fixed in 6.12.117-1
  • linuxDebian:12all versions · no fixed version listed

14 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.2 · 6.18.61 · 6.12.117 · 5.20 · 5.19 · 5.16

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-16
Last Modified
2026-11-19
NVD status
Received
GitHub Advisory
GHSA-772j-v3x2-5prg

Frequently asked questions

What is CVE-2026-99309?

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix overflow in dacloffset bounds check in build_sec_desc() When the large dacl_offset is provided, dacl_offset + sizeof(struct smb_acl) overflows on 32-bit builds and the check is passed, Which makes le16_to_cpu(ppdacl_ptr->size) read out-of-bounds. This only happens for dacl_offset in range [0xFFFFFFF8, 0xFFFFFFFF]. So the oob read is max 8 bytes preceding the allocated ppntsd. unsigned int dacl_offset = le32_to_cpu(ppntsd->dacloffset); int ppdacl_size, ntacl_size = ppntsd_size - dacl_offset; if (!dacl_offset || (dacl_offset + sizeof(struct smb_acl) > ppntsd_size)) goto out; Commit beff0bc9d69b ("ksmbd: fix overflow in dacloffset bounds check") fixes similar checks in other functions. But leaves this one out, because it is only valid for 32-bit builds. Reproduced on 32-bit ARM with KASAN, by a client sending SMB2 SET_INFO(SEC) with dacloffset=0xfffffff8, then QUERY_INFO(SEC) on the same file: BUG: KASAN: slab-out-of-bounds in build_sec_desc (fs/smb/server/smbacl.c:1105) Read of size 2 at addr c2a273fa by task kworker/1:1/35 CPU: 1 UID: 0 PID: 35 Comm: kworker/1:1 Not tainted 7.3.0-rc2+ #5 Workqueue: ksmbd-io handle_ksmbd_work Call trace: kasan_check_range from build_sec_desc (fs/smb/server/smbacl.c:1105) build_sec_desc from smb2_query_info (fs/smb/server/smb2pdu.c:7676) smb2_query_info from handle_ksmbd_work (fs/smb/server/server.c:160) handle_ksmbd_work from process_one_work (kernel/workqueue.c:3401) process_one_work from worker_thread (kernel/workqueue.c:3473) worker_thread from kthread (kernel/kthread.c:436) Add overflow check.

Is CVE-2026-99309 actively exploited?

Active exploitation of CVE-2026-99309 has not been confirmed. Its EPSS score was 0.2% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99309?

CVE-2026-99309 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record