Skip to main content
Menu
CVEs

CVE

Linux kernel out-of-bounds read in ksmbd DACL offset check

CVE-2026-99309EUVD-2026-126215GHSA-772J-V3X2-5PRG

Exploited
No known exploitation
Fix
Fixed in 5.16, 5.19, 5.20
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.16, 5.19, 5.20.

Published
Last modified
Reference
Last checked
0.21% · 11th percentile
20/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The Linux kernel's ksmbd file server has a bounds-check flaw in how it builds security descriptors on 32-bit builds. A client sending a crafted SMB request with a very large DACL offset can make the kernel read memory outside the allocated buffer.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original 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.

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 5.16, 5.19, 5.20.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99309 (ksmbd: fix overflow in dacloffset bounds check in build_sec_desc()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99309 (entry last updated 2026-11-16):
Affected:
- Linux Linux: from 5.15.62, fixed in 5.16; from 5.18.18, fixed in 5.19; from 5.19.2, fixed in 5.20
- Linux Linux: versions 6.0
Fixed versions: 5.16, 5.19, 5.20.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99309 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99309 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/bd92e03122f33c159b552867a4abc098d405dfed
- https://git.kernel.org/stable/c/4f238380ea3803afdc815c615521c6f6b13989a3
- https://git.kernel.org/stable/c/d1e92aa651caa352261fb3b78460b7722357835c
- https://git.kernel.org/stable/c/eb96e2a0e817807c48dc8387ca6a5249fdeae3a0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99309
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99309"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Linux Linux

    From 5.15.62 · fixed in 5.16; From 5.18.18 · fixed in 5.19; From 5.19.2 · fixed in 5.20

  • Linux Linux

    6.0

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Link
  2. Link
  3. Link
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-99309

Is CVE-2026-99309 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-99309?

Linux: from 5.15.62 before 5.16; from 5.18.18 before 5.19; from 5.19.2 before 5.20. Linux: version 6.0.Source: cve.now feed data

How do I fix CVE-2026-99309?

Upgrade to a fixed version: 5.16, 5.19, 5.20.Source: cve.now feed data