CVE-2026-93794smb/client: flush dirty data before punching a hole
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% 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: smb/client: flush dirty data before punching a hole Punching a hole after a large buffered write may leave the range reported as data. Reproduce it with: xfs_io -f \ -c "pwrite -b 3m -S 0x61 0 3m" \ -c "fpunch 1m 1m" \ -c "seek -h 0" \ -c "seek -d 1m" \ /mnt/test/repro Punching 1 MiB at offset 1 MiB should produce: 0 1 MiB 2 MiB 3 MiB | DATA | HOLE | DATA | EOF Instead, the entire file is reported as data. SEEK_HOLE(0) returns EOF, and SEEK_DATA(1M) returns 1M. This happens because a dirty folio spanning the punched range can be written back after the punch and refill the hole. Fix this by flushing and waiting for dirty data in the punched range before invalidating the page cache and issuing FSCTL_SET_ZERO_DATA. The xfstests generic/539 pass against Samba/ksmbd with this change.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 36 days later
· 36 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 – < 0c9fcab9bf1ef3516983f3de05a19c5658c7a01e
- affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 – < 216e469586057c29409e4ef8311d282388c6e251
- affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 – < 6c265aca08155e519a8f6f6071c59dff4f535f70
- affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 – < 39562a56cdb515f6635c3e7bfe6629439b18a169
- affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 – < d7d2adcd022baade5cab65ca492ce63421ce3a6e
- affected 3.17
- unaffected < 3.17
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/0c9fcab9bf1ef3516983f3de05a19c5658c7a01e (opens in a new tab)
- https://git.kernel.org/stable/c/216e469586057c29409e4ef8311d282388c6e251 (opens in a new tab)
- https://git.kernel.org/stable/c/6c265aca08155e519a8f6f6071c59dff4f535f70 (opens in a new tab)
- https://git.kernel.org/stable/c/39562a56cdb515f6635c3e7bfe6629439b18a169 (opens in a new tab)
- https://git.kernel.org/stable/c/d7d2adcd022baade5cab65ca492ce63421ce3a6e (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-86181 (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-93794)Record last updated .