CVE-2026-93794: Linux kernel · smb/client: flush dirty data before punching a hole
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d7d2adcd022baade5cab65ca492ce63421ce3a6e : update Linux kernel when convenient.
Data as of 30 Oct 2026, 12:50 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 is available and has been applied in the Linux kernel. Users should update to the fixed kernel versions identified by the commit hashes provided. No additional mitigation steps are required beyond applying the official fix.
Description
A vulnerability in the Linux kernel SMB client was fixed by ensuring dirty data is flushed before punching a hole in a file. Without this fix, punching a hole after a large buffered write could cause the file range to be incorrectly reported as data instead of a hole. This occurs because dirty data overlapping the punched range might be written back after the hole is punched, refilling it erroneously. The fix flushes and waits for dirty data in the punched range before invalidating the page cache and issuing the zero-data command.
References
- 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/6c265aca08155e519a8f6f6071c59dff4f535f70 (opens in a new tab)
- git.kernel.org/stable/c/39562a56cdb515f6635c3e7bfe6629439b18a169 (opens in a new tab)
- git.kernel.org/stable/c/d7d2adcd022baade5cab65ca492ce63421ce3a6e (opens in a new tab)