CVE-2026-99339: Linux kernel · KVM: x86: Zero reserved synic flags when delivering message to avoid stack leak
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fd7764eea189053ce6345950f11e4aeecd741fba : update Linux kernel when convenient.
Data as of 19 Nov 2026, 14:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fd7764eea189053ce6345950f11e4aeecd741fba, ab15e4093e2aff170ea2087ab994f64530a13cba, 2616f497506a772db53e7bb1024cde50b4c165e0 +1
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 fd7764eea189053ce6345950f11e4aeecd741fba, ab15e4093e2aff170ea2087ab994f64530a13cba, 2616f497506a772db53e7bb1024cde50b4c165e0 or 416da9d1824cf34c709f3222f5012714810734dd.
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– |
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Zero reserved synic flags when delivering message to avoid stack leak Ensure all reserved flags are zeroed when setting the msg_pending flag as part of SynIC message delivery, as setting only msg_pending can leak seven bits of kernel stack data to the guest. E.g. gcc typically uses a bitwise-OR to set the msg_pending flag, without initializing the on-stack variable. Precisely zero the flags, e.g. as opposed to zeroing the entire structure, to make it somewhat more obvious that the flags *need* to be zeroed. E.g. it would be quite easy to misread the initial read of guest memory and think that zeroing the entire structure is completely superfluous.
References
- git.kernel.org/stable/c/fd7764eea189053ce6345950f11e4aeecd741fba (opens in a new tab)
- git.kernel.org/stable/c/ab15e4093e2aff170ea2087ab994f64530a13cba (opens in a new tab)
- git.kernel.org/stable/c/416da9d1824cf34c709f3222f5012714810734dd (opens in a new tab)
- git.kernel.org/stable/c/2616f497506a772db53e7bb1024cde50b4c165e0 (opens in a new tab)