Look up another CVE · open CVE-2026-64136 in the interactive tracker
CVE-2026-64136
smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked()
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem fs/smb. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-64136 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.94-1 | Update the kernel and reboot. Fixed in 6.12.94-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Commit 96c4af418586 ("cifs: Fix locking usage for tcon fields") refactored cifs code to change cifs_tcp_ses_lock for tc_lock around tc_count changes. There was missing lock around tc_count increment inside smb2_find_smb_sess_tcon_unlocked().
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
fs/smb/client/smb2transport.c
- What this is
- COMMON INTERNET FILE SYSTEM CLIENT (CIFS and SMB3)MAINTAINERS section matched on fs/smb/client/ · linux-cifs@vger.kernel.org · Supported
- Kernel module
- cifs
Check it on the machine
grep -wE 'CONFIG_CIFS|CONFIG_SMBFS' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w cifsPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this as a loadable module. Every release below compiles it as a module on every flavour, so whether the code is in the running kernel depends on whether that module is loaded.
- bookworm, trixie, forky, sidm
- m
- a loadable module on every flavour - check lsmod, can be blacklisted
- Build switches
- CONFIG_CIFS, CONFIG_SMBFS
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-07-19 (3 months ago)source
- CVSS
- 9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.49%, higher than 40.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- fs/smb
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.6.128 | 6.6.142 | 7df1df6f40c0 |
| 6.12.75 | 6.12.92 | 13fb413ae22a |
| 6.18.16 | 6.18.34 | bf4ebdb19ff9 |
| 7.0 | 7.0.11 | e374f4e496fe |
| 7.0 | 7.1 | 4d8690dace00 |
| 6.19.6 | 0 | 0 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:NAttack vector, network
- The flaw is in the in-kernel SMB/CIFS client (fs/smb/client/), reached when processing SMB2 responses received over TCP from a remote server in cifs_demultiplex_thread(). A network-positioned attacker controlling or impersonating the SMB server can drive the vulnerable cancelled-mid handling path.
- AC:LAttack complexity, low
- The attacker controls SMB response timing and can trigger concurrent cifs_put_tcon() via server-initiated disconnect/reconnect, racing the unprotected tc_count increment. Cancelled-mid conditions arise from normal concurrent I/O, signals, and unmount/reconnect activity that the attacker can reliably provoke.
- PR:NPrivileges required, none
- Exploitation requires no local privileges on the victim; a remote malicious or compromised SMB server can attack any client that has an active CIFS mount/session, without the attacker holding an account or capabilities on the victim host.
- UI:NUser interaction, none
- No victim interaction is needed at exploit time in common deployments where CIFS shares are automounted at boot or persistently connected (cloud file shares, enterprise NAS); the attacker abuses an already-established SMB session rather than requiring a new mount action.
- S:UScope, unchanged
- Impact is kernel memory corruption and potential local privilege escalation within the same kernel security domain, not a cross-boundary escape such as guest-to-host VM breakout.
- C:HConfidentiality impact, high
- The race can cause a use-after-free of struct cifs_tcon; UAF of kernel heap objects enables arbitrary memory disclosure through controlled reuse of the freed structure.
- I:HIntegrity impact, high
- The UAF leads to subsequent kernel operations (SMB2_close, workqueue handlers) on freed memory, providing a path to arbitrary kernel write and potential code execution via heap grooming.
- A:HAvailability impact, high
- Winning the refcount race causes use-after-free of cifs_tcon with continued kernel use of the freed object, which can trigger kernel oops/panic and denial of service even before full exploitation.