CVE-2026-93794: Linux kernel · smb/client: flush dirty data before punching a hole
Source GCVE Database
Not known to be exploited · fixed in d7d2adcd022baade5cab65ca492ce63421ce3a6e : update Linux kernel when convenient.
Data as of 30 Oct 2026, 17:53 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in d7d2adcd022baade5cab65ca492ce63421ce3a6e, 39562a56cdb515f6635c3e7bfe6629439b18a169, 216e469586057c29409e4ef8311d282388c6e251 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to flush dirty data before punching a hole in the file. Users should apply the official kernel update containing this fix once available. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's SMB client handling could cause file hole punching operations to incorrectly report data ranges. Specifically, after a large buffered write, punching a hole in a file may leave the range reported as data instead of a hole due to dirty data not being flushed properly before the hole is punched. This issue has been resolved by ensuring dirty data in the punched range is flushed and waited on before invalidating the page cache and issuing the zero data operation.
References
- nvd.nist.gov/vuln/detail/CVE-2026-93794 (opens in a new tab)
- git.kernel.org/stable/c/0c9fcab9bf1ef3516983f3de05a19c5658c7a01e (opens in a new tab)
- git.kernel.org/stable/c/216e469586057c29409e4ef8311d282388c6e251 (opens in a new tab)
- git.kernel.org/stable/c/39562a56cdb515f6635c3e7bfe6629439b18a169 (opens in a new tab)
- git.kernel.org/stable/c/6c265aca08155e519a8f6f6071c59dff4f535f70 (opens in a new tab)
- git.kernel.org/stable/c/d7d2adcd022baade5cab65ca492ce63421ce3a6e (opens in a new tab)