CVE-2026-64399
What it is
In the Linux kernel, the following vulnerability has been resolved: ksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE The FSCTL_DUPLICATE_EXTENTS_TO_FILE arm of smb2_ioctl() overwrites the destination file's data via vfs_clone_file_range() with neither the share-level KSMBD_TREE_CONN_FLAG_WRITABLE check nor a per-handle fp->daccess check that the other write-bearing arms carry. A client can overwrite destination data on a read-only share, or from a handle opened with only FILE_WRITE_ATTRIBUTES (which still yields an FMODE_WRITE filp). FILE_WRITE_ATTRIBUTES-only destination handle overwrote the file's data via the clone. Add both checks, matching the FSCTL_SET_SPARSE permission fix; require FILE_WRITE_DATA since this writes data.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, 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: 9.8 CRITICAL (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 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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-64399.md and follow it. Check whether this project is affected by CVE-2026-64399. 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/388e4139db27a9e3612c9d356b826f5b1ff6a9e3
- https://git.kernel.org/stable/c/620d133d469295ee7c017ca6aafac335f65c4a5a
- https://git.kernel.org/stable/c/9b9cf7e65cbeaae1b6636144bacee611cdd7a5d6
- https://git.kernel.org/stable/c/baae7b39673ec21073a25e3d14f8feaada01d5df
- https://git.kernel.org/stable/c/bf460ad5958d506492de4524a656439da3f99c51
- https://git.kernel.org/stable/c/c917e4522d251071dde9871b9142d8ea1186ebfe
References
- https://git.kernel.org/stable/c/388e4139db27a9e3612c9d356b826f5b1ff6a9e3
- https://git.kernel.org/stable/c/620d133d469295ee7c017ca6aafac335f65c4a5a
- https://git.kernel.org/stable/c/9b9cf7e65cbeaae1b6636144bacee611cdd7a5d6
- https://git.kernel.org/stable/c/baae7b39673ec21073a25e3d14f8feaada01d5df
- https://git.kernel.org/stable/c/bf460ad5958d506492de4524a656439da3f99c51
- https://git.kernel.org/stable/c/c917e4522d251071dde9871b9142d8ea1186ebfe