CVE-2026-99562: Linux kernel · ksmbd: reject FSCTL_SET_ZERO_DATA on a directory handle
Source GCVE Database
Not known to be exploited : upgrade to ef85bad39cf273a8377722c9f3078294dcc2fc7a or 89092aa492f1ff8cbbca14503a008795251bae6d soon.
Data as of 19 Nov 2026, 16:29 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in ef85bad39cf273a8377722c9f3078294dcc2fc7a, 89092aa492f1ff8cbbca14503a008795251bae6d
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 18 Nov 2026.
What to do
Upgrade Linux kernel to ef85bad39cf273a8377722c9f3078294dcc2fc7a or 89092aa492f1ff8cbbca14503a008795251bae6d.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Debiandebian/linuxpkg:deb/debian/linuxOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability has been resolved in the Linux kernel by adding checks to reject FSCTL_SET_ZERO_DATA on directory handles in ksmbd_vfs_zero_data(). Users should apply the official kernel updates that include this fix.
Description
CVE-2026-99562 is a vulnerability in the Linux kernel's ksmbd component where an authenticated client with write permissions can cause a kernel panic by sending FSCTL_SET_ZERO_DATA on a directory handle. This occurs because the handler incorrectly allows this operation on directories, leading to a kernel write operation without proper write mode, triggering a panic.