CVE-2026-64398ksmbd: add a permission check for FSCTL_SET_ZERO_DATA
- 8.1HighCVSS base score
- 0.46%Exploitation in 30 daysEPSS · top 59% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 23 days later
· 23 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.46% · top 59% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.
Affected products
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 25377f369688dd0bd814dc8965ed26d44238ecaa
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 3072d82461f498c85daea8766e9d8bfbada31605
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < ca53bb17f4e8232cfaece3953d3cef62c559b039
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 57f2042fd87d7ce8fc3ac8b6c176e554df68b1a7
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < deffa929086d7902e30918adf3dd27ccfe9c08b1
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 3320ba068198adc144c89d6661b805acce01735b
- affected 5.15
- unaffected < 5.15
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/25377f369688dd0bd814dc8965ed26d44238ecaa (opens in a new tab)
- https://git.kernel.org/stable/c/3072d82461f498c85daea8766e9d8bfbada31605 (opens in a new tab)
- https://git.kernel.org/stable/c/ca53bb17f4e8232cfaece3953d3cef62c559b039 (opens in a new tab)
- https://git.kernel.org/stable/c/57f2042fd87d7ce8fc3ac8b6c176e554df68b1a7 (opens in a new tab)
- https://git.kernel.org/stable/c/deffa929086d7902e30918adf3dd27ccfe9c08b1 (opens in a new tab)
- https://git.kernel.org/stable/c/3320ba068198adc144c89d6661b805acce01735b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48942 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64398)Record last updated .