Look up another CVE · open CVE-2026-89632 in the interactive tracker
CVE-2026-89632
smb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr()
Published 2026-09-11 (37 days 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-89632 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 | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | not affected | 7.2.11-1 | Nothing to do. forky never shipped the vulnerable code. |
| Debian unstablesid | not affected | 7.2.11-1 | Nothing to do. sid never shipped the vulnerable code. |
The vulnerability
What the bug is
reparse_buf_ptr() reads buf->ReparseDataLength before checking that count covers the full fixed header: buf = (struct reparse_data_buffer *)((u8 *)io + off); len = sizeof(*buf); /* 8 bytes */ rdlen = le16_to_cpu(buf->ReparseDataLength); /* offset 4, 2 bytes */ if (count < len || count < rdlen + len) /* check comes after */ struct reparse_data_buffer has ReparseDataLength at offset 4. If a server returns OutputCount < 6, the read at offset 4-5 reaches past the end of the received data. The off+count bounds against iov_len were already validated, but that does not protect against count being smaller than sizeof(*buf). Split the check: verify count >= sizeof(*buf) before reading ReparseDataLength, then verify count covers the data region.
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/smb2inode.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-09-11 (37 days ago)source
- CVSS
- 8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.45%, higher than 37.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.32 | 7.2.4 | 711cf71300d7 |
| 6.6.32 | 7.3 | 05f78e6cf34e |
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 client parser for FSCTL_GET_REPARSE_POINT IOCTL replies on TCP/445. A malicious, compromised, or on-path SMB server reaches reparse_buf_ptr() with crafted OutputOffset/OutputCount; this matches sibling client response-parsing scores such as CVE-2026-46155 and CVE-2024-49996.
- AC:LAttack complexity, low
- The server fully controls OutputOffset and OutputCount. A successful IOCTL PDU with OutputCount < 6 and OutputOffset near iov_len (for example a 448-byte cifs_small_rq-sized frame) deterministically loads ReparseDataLength past the received payload, with no race or attacker-uncontrollable layout.
- PR:NPrivileges required, none
- The attacker is the remote SMB server (or a MITM on an unsigned session) and needs no account, credentials, or capabilities on the victim client. GET_REPARSE runs on an already established tree connect after ordinary CREATE/lookup; the client authenticates to the server, not the reverse.
- UI:NUser interaction, none
- On an already-mounted or automounted CIFS share, any routine lookup/stat of a reparse point — including files the server flags as reparse in CREATE — issues FSCTL_GET_REPARSE_POINT. Backup jobs, indexers, and inode revalidation hit the parser with no contemporaneous victim mount action.
- S:UScope, unchanged
- The two-byte out-of-bounds load and any resulting oops stay inside the client kernel's security authority. The bug does not cross a VM, IOMMU, or sandbox boundary.
- C:LConfidentiality impact, low
- The use-before-check reads exactly two bytes of ReparseDataLength past the IOCTL output region (and, when the PDU fills cifs_small_rq, past that 448-byte slab). Those bytes are passed only to smb_EIO2 tracing, so disclosure is strictly bounded, matching CVE-2026-64448 rather than unbounded heap leaks.
- I:NIntegrity impact, none
- The out-of-bounds access is a u16 load used only in the subsequent length check and error trace. On failure the helper returns -EIO and does not install a reparse tag or copy payload, so there is no kernel write or metadata-corruption primitive.
- A:HAvailability impact, high
- A PDU that fills the cifs_small_rq or cifs_request slab with OutputOffset at the object end makes the two-byte load a true slab-out-of-bounds access, which KASAN reports as a BUG and which can oops/panic if the next page is unmapped. A malicious server can retrigger it on every GET_REPARSE.