Skip to main content
Menu
CVEs

Linux kernel out-of-bounds read and cross-share reconnect in ksmbd

CVE-2026-99541Published November 19, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 6.7
Who is exposed
Not reported

Summary

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

ksmbd: fix OOB read and cross-share confusion in ksmbd_validate_name_reconnect()

ksmbd_validate_name_reconnect() indexes ab_pathname[share->path_sz + 1] without checking that the path is longer than share->path_sz + 1 (d_path() fills the buffer from the end). A durable fp is not bound to its original share, so a client can preserve a file from a short-path share and reconnect it on a long-path share, making strcmp() read past the PATH_MAX buffer - with a long enough share path this oopses the kernel, and on a mapped page it also gives a byte-equality oracle on adjacent heap (the reconnect succeeds exactly when the out-of-bounds string equals the requested name). A same-share variant with the durable fp at the share root reads 1 byte past the buffer (strlen(ab_pathname) == share->path_sz).

Check before comparing: the path must be longer than share->path_sz, it must start with share->path, and the next character must be '/'. The share root itself is accepted only for an empty name.

What to do

Upgrade to a fixed version: 6.7.

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-99541 (ksmbd: fix OOB read and cross-share confusion in ksmbd_validate_name_reconnect()), 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-99541 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 6.6.32, fixed in 6.7
- Linux Linux: versions 6.9
Fixed versions: 6.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99541 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99541 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/0129f7196a05a974bfb3ac4efd8380be651a51b9
- https://git.kernel.org/stable/c/93cb902b0ca04c9dc28b38776f7a03503c84b7ad
- https://git.kernel.org/stable/c/828c02c65e2b0541f0cce403e336b978f92b6dfa
- https://git.kernel.org/stable/c/783a7fc454991544bf92268d8f2413af1a7c7eb8
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-99541
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-99541"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • 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

Timeline

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

Evidence 6

Questions about CVE-2026-99541

Is CVE-2026-99541 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-99541?

Linux: from 6.6.32 before 6.7. Linux: version 6.9.

Source: cve.now feed data

How do I fix CVE-2026-99541?

Upgrade to a fixed version: 6.7.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.