Skip to main content
Menu
CVEs

Linux kernel share root deletion via empty path in ksmbd

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

Exploited
No known exploitation
Fix
Fixed in 5.16, 6.2, 6.4
Who is exposed
Not reported

Summary

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

ksmbd: prevent share root removal through empty paths

A FileLinkInformation request can supply "/" as the new link name. smb2_get_name() strips the trailing slash and passes an empty string to ksmbd_vfs_kern_path_start_removing().

ksmbd_vfs_path_lookup() resolves an empty pathname as the configured share path, without LOOKUP_BENEATH. With ReplaceIfExists set, smb2_create_link() can therefore remove the share root from its parent before link creation fails. An authenticated client with a writable share and DELETE access to a file can trigger this if the share root is empty and the mapped user has write and search permission on its parent directory.

Return -EINVAL for empty pathnames when for_remove is set, before resolving the share path or acquiring removal resources. Ordinary lookups continue to accept empty pathnames for opening the share root.

What to do

Upgrade to a fixed version: 5.16, 6.2, 6.4.

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-99535 (ksmbd: prevent share root removal through empty paths), 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-99535 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 5.15.145, fixed in 5.16; from 6.1.71, fixed in 6.2; from 6.3.10, fixed in 6.4
- Linux Linux: versions 6.4
Fixed versions: 5.16, 6.2, 6.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99535 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99535 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/007eaa56b06fd05c55b86afabab3354ff7c24653
- https://git.kernel.org/stable/c/2756a41a82d618bf1d8b41d74108311815cb695c
- https://git.kernel.org/stable/c/1f8945d2eb20a135b4e22e6fe2348a0191be208a
- https://git.kernel.org/stable/c/9fd1fcbbf84986a7bcf601a2b90540899069d263
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-99535
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-99535"}.

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-99535

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

Linux: from 5.15.145 before 5.16; from 6.1.71 before 6.2; from 6.3.10 before 6.4. Linux: version 6.4.

Source: cve.now feed data

How do I fix CVE-2026-99535?

Upgrade to a fixed version: 5.16, 6.2, 6.4.

Source: cve.now feed data

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