KVM: x86: Zero reserved synic flags when delivering message to avoid stack leak
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fd7764eea189053ce6345950f11e4aeecd741fba, Kernel 2616f497506a772db53e7bb1024cde50b4c165e0, Kernel 416da9d1824cf34c709f3222f5012714810734dd and 4 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3a0e7731724f6ac684129f1763eef4d2d3e7dec7 <fd7764eea189053ce6345950f11e4aeecd741fba, >=3a0e7731724f6ac684129f1763eef4d2d3e7dec7 <2616f497506a772db53e7bb1024cde50b4c165e0, >=3a0e7731724f6ac684129f1763eef4d2d3e7dec7 <416da9d1824cf34c709f3222f5012714810734dd, >=3a0e7731724f6ac684129f1763eef4d2d3e7dec7 <ab15e4093e2aff170ea2087ab994f64530a13cba, =5.0 | fd7764eea189053ce6345950f11e4aeecd741fba, 2616f497506a772db53e7bb1024cde50b4c165e0, 416da9d1824cf34c709f3222f5012714810734dd, ab15e4093e2aff170ea2087ab994f64530a13cba |
| linux-kernel: Kernel | >=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.0.0 <6.12.117 | 6.18.61, 7.3.2, 6.12.117 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket