CVE-2021-47110
published 2024-03-15CVE-2021-47110: In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Disable kvmclock on all CPUs on shutdown Currenly, we disable kvmclock from…
PriorityP429high7.1CVSS 3.1
AVLACLPRLUINSUCHINAH
EPSS
0.24%
15.9th percentile
In the Linux kernel, the following vulnerability has been resolved:
x86/kvm: Disable kvmclock on all CPUs on shutdown
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.
Note, writing '0' to kvmclock MSR doesn't clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don't need to switch to some other clocksource.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.46-1 (bookworm) | linux 5.10.46-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 1e977aa12dd4f80688b1f243762212e75c6d7fe8 < 9084fe1b3572664ad276f427dce575f580c9799a | 9084fe1b3572664ad276f427dce575f580c9799a |
| linux | linux | >= 1e977aa12dd4f80688b1f243762212e75c6d7fe8 < 3b0becf8b1ecf642a9edaf4c9628ffc641e490d6 | 3b0becf8b1ecf642a9edaf4c9628ffc641e490d6 |
| linux | linux | >= 1e977aa12dd4f80688b1f243762212e75c6d7fe8 < 1df2dc09926f61319116c80ee85701df33577d70 | 1df2dc09926f61319116c80ee85701df33577d70 |
| linux | linux | >= 1e977aa12dd4f80688b1f243762212e75c6d7fe8 < c02027b5742b5aa804ef08a4a9db433295533046 | c02027b5742b5aa804ef08a4a9db433295533046 |
| linux | linux_kernel | < 5.4.125 | 5.4.125 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 0 < 5.10.46-1 | 5.10.46-1 |
| linux | linux_kernel | >= 5.11 < 5.12.10 | 5.12.10 |
| linux | linux_kernel | >= 5.5 < 5.10.43 | 5.10.43 |
CVSS provenance
nvdv3.17.1HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
osv7.1HIGH
vendor_debian7.1HIGH
vendor_redhat7.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: x86/kvm: Disable kvmclock on all CPUs on shutdown
vendor_redhat·2024-03-15·CVSS 7.1
CVE-2021-47110 [HIGH] CWE-99 kernel: x86/kvm: Disable kvmclock on all CPUs on shutdown
kernel: x86/kvm: Disable kvmclock on all CPUs on shutdown
In the Linux kernel, the following vulnerability has been resolved:
x86/kvm: Disable kvmclock on all CPUs on shutdown
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.
Note, writing '0' to kvmclock MSR doesn't clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don't need to switch to some other clocksource.
Package: kernel (Red Hat Enterprise Linux 6) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 7) - Out of support scope
Package: ke
Debian
CVE-2021-47110: linux - In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Di...
vendor_debian·2021·CVSS 7.1
CVE-2021-47110 [HIGH] CVE-2021-47110: linux - In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Di...
In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Disable kvmclock on all CPUs on shutdown Currenly, we disable kvmclock from machine_shutdown() hook and this only happens for boot CPU. We need to disable it for all CPUs to guard against memory corruption e.g. on restore from hibernate. Note, writing '0' to kvmclock MSR doesn't clear memory location, it just prevents hypervisor from updating the location so for the short while after write and while CPU is still alive, the clock remains usable and correct so we don't need to switch to some other clocksource.
Scope: local
bookworm: resolved (fixed in 5.10.46-1)
bullseye: resolved (fixed in 5.10.46-1)
forky: resolved (fixed in 5.10.46-1)
sid: resolved (fixed in 5.10.46-1)
trixie: resolved (fixed in 5.10.46-1)
OSV
CVE-2021-47110: In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Disable kvmclock on all CPUs on shutdown Currenly, we disable kvmclock fr
osv·2024-03-15·CVSS 7.1
CVE-2021-47110 [HIGH] CVE-2021-47110: In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Disable kvmclock on all CPUs on shutdown Currenly, we disable kvmclock fr
In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Disable kvmclock on all CPUs on shutdown Currenly, we disable kvmclock from machine_shutdown() hook and this only happens for boot CPU. We need to disable it for all CPUs to guard against memory corruption e.g. on restore from hibernate. Note, writing '0' to kvmclock MSR doesn't clear memory location, it just prevents hypervisor from updating the location so for the short while after write and while CPU is still alive, the clock remains usable and correct so we don't need to switch to some other clocksource.
GHSA
GHSA-hx76-chvw-qr8x: In the Linux kernel, the following vulnerability has been resolved:
x86/kvm: Disable kvmclock on all CPUs on shutdown
Currenly, we disable kvmclock
ghsa_unreviewed·2024-03-15
CVE-2021-47110 [HIGH] CWE-459 GHSA-hx76-chvw-qr8x: In the Linux kernel, the following vulnerability has been resolved:
x86/kvm: Disable kvmclock on all CPUs on shutdown
Currenly, we disable kvmclock
In the Linux kernel, the following vulnerability has been resolved:
x86/kvm: Disable kvmclock on all CPUs on shutdown
Currenly, we disable kvmclock from machine_shutdown() hook and this
only happens for boot CPU. We need to disable it for all CPUs to
guard against memory corruption e.g. on restore from hibernate.
Note, writing '0' to kvmclock MSR doesn't clear memory location, it
just prevents hypervisor from updating the location so for the short
while after write and while CPU is still alive, the clock remains usable
and correct so we don't need to switch to some other clocksource.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/1df2dc09926f61319116c80ee85701df33577d70https://git.kernel.org/stable/c/3b0becf8b1ecf642a9edaf4c9628ffc641e490d6https://git.kernel.org/stable/c/9084fe1b3572664ad276f427dce575f580c9799ahttps://git.kernel.org/stable/c/c02027b5742b5aa804ef08a4a9db433295533046https://git.kernel.org/stable/c/1df2dc09926f61319116c80ee85701df33577d70https://git.kernel.org/stable/c/3b0becf8b1ecf642a9edaf4c9628ffc641e490d6https://git.kernel.org/stable/c/9084fe1b3572664ad276f427dce575f580c9799ahttps://git.kernel.org/stable/c/c02027b5742b5aa804ef08a4a9db433295533046
2024-03-15
Published