CVE-2026-64398
What it is
In the Linux kernel, the following vulnerability has been resolved: ksmbd: add a permission check for FSCTL_SET_ZERO_DATA FSCTL_SET_ZERO_DATA in smb2_ioctl() destroys file data via ksmbd_vfs_zero_data() -> vfs_fallocate(PUNCH_HOLE/ZERO_RANGE) after checking only the share-level KSMBD_TREE_CONN_FLAG_WRITABLE, with no per-handle access check. A handle opened with only FILE_WRITE_ATTRIBUTES still yields an FMODE_WRITE filp (FILE_WRITE_ATTRIBUTES is part of FILE_WRITE_DESIRE_ACCESS_LE, so smb2_create_open_flags() opens it O_WRONLY), so the vfs_fallocate FMODE_WRITE check does not stop it; only the missing fp->daccess gate would. Reproduced on mainline 7.1-rc7 with KASAN by an authenticated SMB client: a FILE_WRITE_ATTRIBUTES-only handle zeroed 4096 bytes of file data it had no FILE_WRITE_DATA right to (6/6; a FILE_READ_DATA-only handle was correctly denied). This is the unfixed sibling of commit cc57232cae23 ("ksmbd: fix FSCTL permission bypass by adding a permission check for FSCTL_SET_SPARSE"). Because SET_ZERO_DATA writes data (not an attribute), require FILE_WRITE_DATA.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data tampering, service disruption.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 8.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.178
- Linux Kernel < 6.6.145
- Linux Kernel < 6.12.96
- Linux Kernel < 6.18.39
- Linux Kernel < 7.1.4
Attack profile CVSS 3.1 · 8.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64398.md and follow it. Check whether this project is affected by CVE-2026-64398. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/25377f369688dd0bd814dc8965ed26d44238ecaa
- https://git.kernel.org/stable/c/3072d82461f498c85daea8766e9d8bfbada31605
- https://git.kernel.org/stable/c/3320ba068198adc144c89d6661b805acce01735b
- https://git.kernel.org/stable/c/57f2042fd87d7ce8fc3ac8b6c176e554df68b1a7
- https://git.kernel.org/stable/c/ca53bb17f4e8232cfaece3953d3cef62c559b039
- https://git.kernel.org/stable/c/deffa929086d7902e30918adf3dd27ccfe9c08b1
References
- https://git.kernel.org/stable/c/25377f369688dd0bd814dc8965ed26d44238ecaa
- https://git.kernel.org/stable/c/3072d82461f498c85daea8766e9d8bfbada31605
- https://git.kernel.org/stable/c/3320ba068198adc144c89d6661b805acce01735b
- https://git.kernel.org/stable/c/57f2042fd87d7ce8fc3ac8b6c176e554df68b1a7
- https://git.kernel.org/stable/c/ca53bb17f4e8232cfaece3953d3cef62c559b039
- https://git.kernel.org/stable/c/deffa929086d7902e30918adf3dd27ccfe9c08b1