Look up another CVE · open CVE-2026-31432 in the interactive tracker
CVE-2026-31432
ksmbd: fix OOB write in QUERY_INFO for compound requests
Published 2026-04-22 (6 months ago) by the Linux kernel CNA. Subsystem fs/smb. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-31432 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 | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixedDSA-6238-1 · 2026-04-30 · text | 6.12.85-1 | Update the kernel and reboot. DSA-6238-1 shipped the fix on 2026-04-30, in 6.12.85-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.19.12-1 | Update the kernel and reboot. Fixed in 6.19.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.19.12-1 | Update the kernel and reboot. Fixed in 6.19.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
When a compound request such as READ + QUERY_INFO(Security) is received, and the first command (READ) consumes most of the response buffer, ksmbd could write beyond the allocated buffer while building a security descriptor. The root cause was that smb2_get_info_sec() checked buffer space using ppntsd_size from xattr, while build_sec_desc() often synthesized a significantly larger descriptor from POSIX ACLs. This patch introduces smb_acl_sec_desc_scratch_len() to accurately compute the final descriptor size beforehand, performs proper buffer checking with smb2_calc_max_out_buf_len(), and uses exact-sized allocation + iov pinning.
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/server/smb2pdu.c
fs/smb/server/smbacl.c
fs/smb/server/smbacl.h
- What this is
- KERNEL SMB3 SERVER (KSMBD)MAINTAINERS section matched on fs/smb/server/ · linux-cifs@vger.kernel.org · Maintained
- Kernel module
- ksmbd
Check it on the machine
grep -wE 'CONFIG_SMBFS|CONFIG_SMB_SERVER' /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 ksmbdPrints 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_SMBFS, CONFIG_SMB_SERVER
- 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-04-22 (6 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.60%, higher than 47.7% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- 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 | 6.6.143 | 850452af77f5 |
| 6.6 | 6.12.81 | d48c64fb80ad |
| 6.6 | 6.18.22 | 075ea208c648 |
| 6.6 | 6.19.12 | 515c2daab460 |
| 6.6 | 7.0 | fda9522ed6af |
| 5.15.145 | 0 | 0 |
| 6.1.71 | 0 | 0 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DSA-6238-1 | 2026-04-30 | trixie 6.12.85-1 | tracker |
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
- ksmbd is the in-kernel SMB server listening on TCP/445, directly reachable over the network by any remote SMB client.
- AC:LAttack complexity, low
- The attacker reliably triggers the OOB write by crafting a compound request (e.g., READ + QUERY_INFO(Security)) where the first command consumes most of the response buffer. No race condition or special conditions are needed.
- PR:LPrivileges required, low
- The QUERY_INFO command requires a valid SMB session (checked by smb2_check_user_session), a tree connect, and an open file handle. Even guest access requires completing session setup, so low privileges are needed.
- UI:NUser interaction, none
- No user interaction is required; the attacker sends the compound request directly to the ksmbd server.
- S:UScope, unchanged
- The vulnerability results in kernel heap corruption within the same security authority (the kernel); no security boundary such as a VM or sandbox is crossed.
- C:HConfidentiality impact, high
- The heap buffer overflow writes past the kvzalloc'd response buffer into adjacent kernel heap objects. This OOB write can be leveraged to corrupt adjacent structures and create information disclosure primitives.
- I:HIntegrity impact, high
- The OOB write corrupts kernel heap memory with attacker-influenced data (security descriptor content including SIDs and ACEs derived from file ACLs), enabling potential control flow hijacking or arbitrary write primitives.
- A:HAvailability impact, high
- The heap buffer overflow corrupts adjacent kernel data structures, reliably causing kernel crashes or panics.