Linux kernel use-after-free in SMB client channel setup
- Exploited
- No known exploitation
- Fix
- Fixed in 6.2, 6.7
- Who is exposed
- Not reported
Summary
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
Upgrade to a fixed version: 6.2, 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-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"}.Affected versions
- Linux LinuxFrom 6.1.178 · fixed in 6.2; From 6.6.15 · fixed in 6.7
- Linux Linux6.7
cve.now Index
- 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
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99525 |
| Record | NVD · CVE-2026-99525 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/d88e3e844fad0f6b9fbeb8c8862f9272a7c26a99 |
| Link | git.kernel.org · stable/c/8069935474b1502459ab50f75a67d7394a93cd5d |
| Link | git.kernel.org · stable/c/72367dacb5c9d8bd486b2fcaf56b6d3086d57250 |
| Link | git.kernel.org · stable/c/031278577380e7875d95aed81a2b2bcac39be923 |
Questions about CVE-2026-99525
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: cve.now feed data
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: cve.now feed data
How do I fix CVE-2026-99525?
Upgrade to a fixed version: 6.2, 6.7.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.