CVE-2026-64398: ksmbd: add a permission check for FSCTL_SET_ZERO_DATA
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 25377f369688dd0bd814dc8965ed26d44238ecaa, 3072d82461f498c85daea8766e9d8bfbada31605, 3320ba068198adc144c89d6661b805acce01735b.
Low priority for now. Upgrade to Linux Linux 25377f369688dd0bd814dc8965ed26d44238ecaa, 3072d82461f498c85daea8766e9d8bfbada31605, 3320ba068198adc144c89d6661b805acce01735b or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- —
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15 and later · before 6.1.178
- linux linux kernel6.2 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.96
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 25377f369688dd0bd814dc8965ed26d44238ecaaaffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 3072d82461f498c85daea8766e9d8bfbada31605affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before ca53bb17f4e8232cfaece3953d3cef62c559b039affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 57f2042fd87d7ce8fc3ac8b6c176e554df68b1a7affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before deffa929086d7902e30918adf3dd27ccfe9c08b1affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 3320ba068198adc144c89d6661b805acce01735baffected · git
- before 5.15not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64396Jul 25, 2026 · ksmbd: fix UAF of struct file_lock in SMB2_LOCK deferred-lock cancellation35Monitor
- ← EarlierCVE-2026-64397Jul 25, 2026 · ksmbd: serialize QUERY_DIRECTORY requests per file39Monitor
- Later →CVE-2026-64399Jul 25, 2026 · ksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 25377f369688dd0bd814dc8965ed26d44238ecaa | Vendor (CNA) |
| Linux Linux | 3072d82461f498c85daea8766e9d8bfbada31605 | Vendor (CNA) |
| Linux Linux | 3320ba068198adc144c89d6661b805acce01735b | Vendor (CNA) |
| Linux Linux | 57f2042fd87d7ce8fc3ac8b6c176e554df68b1a7 | Vendor (CNA) |
| Linux Linux | ca53bb17f4e8232cfaece3953d3cef62c559b039 | Vendor (CNA) |
| Linux Linux | deffa929086d7902e30918adf3dd27ccfe9c08b1 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3072d82461f498c85daea8766e9d8bfbada31605
- git.kernel.org/stable/c/3320ba068198adc144c89d6661b805acce01735b
- git.kernel.org/stable/c/57f2042fd87d7ce8fc3ac8b6c176e554df68b1a7
- git.kernel.org/stable/c/ca53bb17f4e8232cfaece3953d3cef62c559b039
- git.kernel.org/stable/c/deffa929086d7902e30918adf3dd27ccfe9c08b1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.