CVE-2021-46990
published 2024-02-28CVE-2021-46990: In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Fix crashes when toggling entry flush barrier The entry flush mitigation can…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
14.0th percentile
In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s: Fix crashes when toggling entry flush barrier
The entry flush mitigation can be enabled/disabled at runtime via a
debugfs file (entry_flush), which causes the kernel to patch itself to
enable/disable the relevant mitigations.
However depending on which mitigation we're using, it may not be safe to
do that patching while other CPUs are active. For example the following
crash:
sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20
Shows that we returned to userspace with a corrupted LR that points into
the kernel, due to executing the partially patched call to the fallback
entry flush (ie. we missed the LR restore).
Fix it by doing the patching under stop machine. The CPUs that aren't
doing the patching will be spinning in the core of the stop machine
logic. That is currently sufficient for our purposes, because none of
the patching we do is to that code or anywhere in the vicinity.
Affected
32 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.38-1 (bookworm) | linux 5.10.38-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 4.14.208 < 4.14.233 | 4.14.233 |
| linux | linux | >= 4.19.159 < 4.19.191 | 4.19.191 |
| linux | linux | >= 4.4.245 < 4.4.269 | 4.4.269 |
| linux | linux | >= 4.9.245 < 4.9.269 | 4.9.269 |
| linux | linux | >= 4a1e90af718d1489ffcecc8f52486c4f5dc0f7a6 < 8382b15864e5014261b4f36c2aa89723612ee058 | 8382b15864e5014261b4f36c2aa89723612ee058 |
| linux | linux | >= 5.4.79 < 5.4.120 | 5.4.120 |
| linux | linux | >= 5.9.10 < 5.10 | 5.10 |
| linux | linux | >= b65458b6be8032c5179d4f562038575d7b3a6be3 < 0b4eb172cc12dc102cd0ad013e53ee4463db9508 | 0b4eb172cc12dc102cd0ad013e53ee4463db9508 |
| linux | linux | >= db01cad9efe3c3838a6b3a3f68affd295c4b92d6 < ee4b7aab93c2631c3bb0753023c5dda592bb666b | ee4b7aab93c2631c3bb0753023c5dda592bb666b |
| linux | linux | >= f69bb4e51f41973fb7594be1479fa689831efe1a < 2db22ba4e0e103f00e0512e0ecce36ac78c644f8 | 2db22ba4e0e103f00e0512e0ecce36ac78c644f8 |
| linux | linux | >= f79643787e0a0762d2409b7b8334e83f22d85695 < d2e3590ca39ccfd8a5a46d8c7f095cb6c7b9ae92 | d2e3590ca39ccfd8a5a46d8c7f095cb6c7b9ae92 |
| linux | linux | >= f79643787e0a0762d2409b7b8334e83f22d85695 < dd0d6117052faace5440db20fc37175efe921c7d | dd0d6117052faace5440db20fc37175efe921c7d |
| linux | linux | >= f79643787e0a0762d2409b7b8334e83f22d85695 < 5bc00fdda1e934c557351a9c751a205293e68cbf | 5bc00fdda1e934c557351a9c751a205293e68cbf |
| linux | linux | >= f79643787e0a0762d2409b7b8334e83f22d85695 < aec86b052df6541cc97c5fca44e5934cbea4963b | aec86b052df6541cc97c5fca44e5934cbea4963b |
| linux | linux | >= fa4bf9f38184ed7ca4916eb64f8c767d1e279c1f < 0c25a7bb697f2e6ee65b6d63782f675bf129511a | 0c25a7bb697f2e6ee65b6d63782f675bf129511a |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 4.4.0-253.287 | 4.4.0-253.287 |
| linux | linux_kernel | >= 4.14.208 < 4.14.233 | 4.14.233 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv7.0HIGH
vendor_ubuntu7.0HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
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.
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2024-04-19·CVSS 7.0
CVE-2023-1382 [HIGH] Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
It was discovered that a race condition existed in the instruction emulator
of the Linux kernel on Arm 64-bit systems. A local attacker could use this
to cause a denial of service (system crash). (CVE-2022-20422)
Wei Chen discovered that a race condition existed in the TIPC protocol
implementation in the Linux kernel, leading to a null pointer dereference
vulnerability. A local attacker could use this to cause a denial of service
(system crash). (CVE-2023-1382)
Jose Oliveira and Rodrigo Branco discovered that the Spectre Variant 2
mitigations with prctl syscall were insufficient in some situations. A
local attacker could possibly use this to expose sensitive information.
(CVE-2023-1998)
Red Hat
kernel: powerpc/64s: Fix crashes when toggling entry flush barrier
vendor_redhat·2024-02-28·CVSS 5.5
CVE-2021-46990 [MEDIUM] CWE-20 kernel: powerpc/64s: Fix crashes when toggling entry flush barrier
kernel: powerpc/64s: Fix crashes when toggling entry flush barrier
In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s: Fix crashes when toggling entry flush barrier
The entry flush mitigation can be enabled/disabled at runtime via a
debugfs file (entry_flush), which causes the kernel to patch itself to
enable/disable the relevant mitigations.
However depending on which mitigation we're using, it may not be safe to
do that patching while other CPUs are active. For example the following
crash:
sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20
Shows that we returned to userspace with a corrupted LR that points into
the kernel, due to executing the partially patched call to the fallback
entry flush (ie. we missed the LR res
Debian
CVE-2021-46990: linux - In the Linux kernel, the following vulnerability has been resolved: powerpc/64s...
vendor_debian·2021·CVSS 5.5
CVE-2021-46990 [MEDIUM] CVE-2021-46990: linux - In the Linux kernel, the following vulnerability has been resolved: powerpc/64s...
In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Fix crashes when toggling entry flush barrier The entry flush mitigation can be enabled/disabled at runtime via a debugfs file (entry_flush), which causes the kernel to patch itself to enable/disable the relevant mitigations. However depending on which mitigation we're using, it may not be safe to do that patching while other CPUs are active. For example the following crash: sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20 Shows that we returned to userspace with a corrupted LR that points into the kernel, due to executing the partially patched call to the fallback entry flush (ie. we missed the LR restore). Fix it by doing the patching under stop machine. The CPUs tha
OSV
linux, linux-aws, linux-kvm, linux-lts-xenial vulnerabilities
osv·2024-04-19·CVSS 7.0
CVE-2022-20422 [HIGH] linux, linux-aws, linux-kvm, linux-lts-xenial vulnerabilities
linux, linux-aws, linux-kvm, linux-lts-xenial vulnerabilities
It was discovered that a race condition existed in the instruction emulator
of the Linux kernel on Arm 64-bit systems. A local attacker could use this
to cause a denial of service (system crash). (CVE-2022-20422)
Wei Chen discovered that a race condition existed in the TIPC protocol
implementation in the Linux kernel, leading to a null pointer dereference
vulnerability. A local attacker could use this to cause a denial of service
(system crash). (CVE-2023-1382)
Jose Oliveira and Rodrigo Branco discovered that the Spectre Variant 2
mitigations with prctl syscall were insufficient in some situations. A
local attacker could possibly use this to expose sensitive information.
(CVE-2023-1998)
Daniele Antonioli discovered that the
GHSA
GHSA-qg29-4gg5-8r2w: In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s: Fix crashes when toggling entry flush barrier
The entry flush mitig
ghsa_unreviewed·2024-02-28
CVE-2021-46990 [MEDIUM] GHSA-qg29-4gg5-8r2w: In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s: Fix crashes when toggling entry flush barrier
The entry flush mitig
In the Linux kernel, the following vulnerability has been resolved:
powerpc/64s: Fix crashes when toggling entry flush barrier
The entry flush mitigation can be enabled/disabled at runtime via a
debugfs file (entry_flush), which causes the kernel to patch itself to
enable/disable the relevant mitigations.
However depending on which mitigation we're using, it may not be safe to
do that patching while other CPUs are active. For example the following
crash:
sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20
Shows that we returned to userspace with a corrupted LR that points into
the kernel, due to executing the partially patched call to the fallback
entry flush (ie. we missed the LR restore).
Fix it by doing the patching under stop machine. The CP
OSV
CVE-2021-46990: In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Fix crashes when toggling entry flush barrier The entry flush mitigat
osv·2024-02-28·CVSS 5.5
CVE-2021-46990 [MEDIUM] CVE-2021-46990: In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Fix crashes when toggling entry flush barrier The entry flush mitigat
In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Fix crashes when toggling entry flush barrier The entry flush mitigation can be enabled/disabled at runtime via a debugfs file (entry_flush), which causes the kernel to patch itself to enable/disable the relevant mitigations. However depending on which mitigation we're using, it may not be safe to do that patching while other CPUs are active. For example the following crash: sleeper[15639]: segfault (11) at c000000000004c20 nip c000000000004c20 lr c000000000004c20 Shows that we returned to userspace with a corrupted LR that points into the kernel, due to executing the partially patched call to the fallback entry flush (ie. we missed the LR restore). Fix it by doing the patching under stop machine. The CPUs tha
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0b4eb172cc12dc102cd0ad013e53ee4463db9508https://git.kernel.org/stable/c/0c25a7bb697f2e6ee65b6d63782f675bf129511ahttps://git.kernel.org/stable/c/2db22ba4e0e103f00e0512e0ecce36ac78c644f8https://git.kernel.org/stable/c/5bc00fdda1e934c557351a9c751a205293e68cbfhttps://git.kernel.org/stable/c/8382b15864e5014261b4f36c2aa89723612ee058https://git.kernel.org/stable/c/aec86b052df6541cc97c5fca44e5934cbea4963bhttps://git.kernel.org/stable/c/d2e3590ca39ccfd8a5a46d8c7f095cb6c7b9ae92https://git.kernel.org/stable/c/dd0d6117052faace5440db20fc37175efe921c7dhttps://git.kernel.org/stable/c/ee4b7aab93c2631c3bb0753023c5dda592bb666bhttps://git.kernel.org/stable/c/0b4eb172cc12dc102cd0ad013e53ee4463db9508https://git.kernel.org/stable/c/0c25a7bb697f2e6ee65b6d63782f675bf129511ahttps://git.kernel.org/stable/c/2db22ba4e0e103f00e0512e0ecce36ac78c644f8https://git.kernel.org/stable/c/5bc00fdda1e934c557351a9c751a205293e68cbfhttps://git.kernel.org/stable/c/8382b15864e5014261b4f36c2aa89723612ee058https://git.kernel.org/stable/c/aec86b052df6541cc97c5fca44e5934cbea4963bhttps://git.kernel.org/stable/c/d2e3590ca39ccfd8a5a46d8c7f095cb6c7b9ae92https://git.kernel.org/stable/c/dd0d6117052faace5440db20fc37175efe921c7dhttps://git.kernel.org/stable/c/ee4b7aab93c2631c3bb0753023c5dda592bb666b
2024-02-28
Published