CVE-2022-49074
published 2025-02-26CVE-2022-49074: In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix GICR_CTLR.RWP polling It turns out that our polling of RWP is totally…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
18.1th percentile
In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3: Fix GICR_CTLR.RWP polling
It turns out that our polling of RWP is totally wrong when checking
for it in the redistributors, as we test the *distributor* bit index,
whereas it is a different bit number in the RDs... Oopsie boo.
This is embarassing. Not only because it is wrong, but also because
it took *8 years* to notice the blunder...
Just fix the damn thing.
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.17.3-1 (bookworm) | linux 5.17.3-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 021f653791ad17e03f98aaa7fb933816ae16f161 < c7daf1b4ad809692d5c26f33c02ed8a031066548 | c7daf1b4ad809692d5c26f33c02ed8a031066548 |
| linux | linux | >= 021f653791ad17e03f98aaa7fb933816ae16f161 < 3c07cc242baf83f0bddbbd9d7945d0bee56d8b57 | 3c07cc242baf83f0bddbbd9d7945d0bee56d8b57 |
| linux | linux | >= 021f653791ad17e03f98aaa7fb933816ae16f161 < ff24114bb08d8b90edf2aff0a4fd0689523e6c17 | ff24114bb08d8b90edf2aff0a4fd0689523e6c17 |
| linux | linux | >= 021f653791ad17e03f98aaa7fb933816ae16f161 < 7218a789abb3e033f5f3a85636ca50d9ae7b0fc9 | 7218a789abb3e033f5f3a85636ca50d9ae7b0fc9 |
| linux | linux | >= 021f653791ad17e03f98aaa7fb933816ae16f161 < 60e1eb4811f53f5f60c788297d978515e7a2637a | 60e1eb4811f53f5f60c788297d978515e7a2637a |
| linux | linux | >= 021f653791ad17e03f98aaa7fb933816ae16f161 < 6fef3e3179e6ed8fecdd004ede541674ffa7749d | 6fef3e3179e6ed8fecdd004ede541674ffa7749d |
| linux | linux | >= 021f653791ad17e03f98aaa7fb933816ae16f161 < 0df6664531a12cdd8fc873f0cac0dcb40243d3e9 | 0df6664531a12cdd8fc873f0cac0dcb40243d3e9 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.113-1 | 5.10.113-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 0 < 5.17.3-1 | 5.17.3-1 |
| linux | linux_kernel | >= 3.17 < 4.19.238 | 4.19.238 |
| linux | linux_kernel | >= 4.20 < 5.4.189 | 5.4.189 |
| linux | linux_kernel | >= 5.11 < 5.15.34 | 5.15.34 |
| linux | linux_kernel | >= 5.16 < 5.16.20 | 5.16.20 |
| linux | linux_kernel | >= 5.17 < 5.17.3 | 5.17.3 |
| linux | linux_kernel | >= 5.5 < 5.10.111 | 5.10.111 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
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.
Red Hat
kernel: irqchip/gic-v3: Fix GICR_CTLR.RWP polling
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49074 [MEDIUM] CWE-20 kernel: irqchip/gic-v3: Fix GICR_CTLR.RWP polling
kernel: irqchip/gic-v3: Fix GICR_CTLR.RWP polling
In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3: Fix GICR_CTLR.RWP polling
It turns out that our polling of RWP is totally wrong when checking
for it in the redistributors, as we test the *distributor* bit index,
whereas it is a different bit number in the RDs... Oopsie boo.
This is embarassing. Not only because it is wrong, but also because
it took *8 years* to notice the blunder...
Just fix the damn thing.
This is a vulnerability in the Linux kernel's ARM Generic Interrupt Controller version 3 (GICv3) implementation, specifically within the irqchip/gic-v3 driver. The issue stems from incorrect polling of the RWP (Register Write Pending) bit in the GICR_CTLR register of the redistributor. The code mista
Debian
CVE-2022-49074: linux - In the Linux kernel, the following vulnerability has been resolved: irqchip/gic...
vendor_debian·2022·CVSS 5.5
CVE-2022-49074 [MEDIUM] CVE-2022-49074: linux - In the Linux kernel, the following vulnerability has been resolved: irqchip/gic...
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix GICR_CTLR.RWP polling It turns out that our polling of RWP is totally wrong when checking for it in the redistributors, as we test the *distributor* bit index, whereas it is a different bit number in the RDs... Oopsie boo. This is embarassing. Not only because it is wrong, but also because it took *8 years* to notice the blunder... Just fix the damn thing.
Scope: local
bookworm: resolved (fixed in 5.17.3-1)
bullseye: resolved (fixed in 5.10.113-1)
forky: resolved (fixed in 5.17.3-1)
sid: resolved (fixed in 5.17.3-1)
trixie: resolved (fixed in 5.17.3-1)
GHSA
GHSA-4m74-wv34-4crh: In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3: Fix GICR_CTLR
ghsa_unreviewed·2025-10-14
CVE-2022-49074 [MEDIUM] GHSA-4m74-wv34-4crh: In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3: Fix GICR_CTLR
In the Linux kernel, the following vulnerability has been resolved:
irqchip/gic-v3: Fix GICR_CTLR.RWP polling
It turns out that our polling of RWP is totally wrong when checking
for it in the redistributors, as we test the *distributor* bit index,
whereas it is a different bit number in the RDs... Oopsie boo.
This is embarassing. Not only because it is wrong, but also because
it took *8 years* to notice the blunder...
Just fix the damn thing.
OSV
CVE-2022-49074: In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix GICR_CTLR
osv·2025-02-26·CVSS 5.5
CVE-2022-49074 [MEDIUM] CVE-2022-49074: In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix GICR_CTLR
In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix GICR_CTLR.RWP polling It turns out that our polling of RWP is totally wrong when checking for it in the redistributors, as we test the *distributor* bit index, whereas it is a different bit number in the RDs... Oopsie boo. This is embarassing. Not only because it is wrong, but also because it took *8 years* to notice the blunder... Just fix the damn thing.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/0df6664531a12cdd8fc873f0cac0dcb40243d3e9https://git.kernel.org/stable/c/3c07cc242baf83f0bddbbd9d7945d0bee56d8b57https://git.kernel.org/stable/c/60e1eb4811f53f5f60c788297d978515e7a2637ahttps://git.kernel.org/stable/c/6fef3e3179e6ed8fecdd004ede541674ffa7749dhttps://git.kernel.org/stable/c/7218a789abb3e033f5f3a85636ca50d9ae7b0fc9https://git.kernel.org/stable/c/c7daf1b4ad809692d5c26f33c02ed8a031066548https://git.kernel.org/stable/c/ff24114bb08d8b90edf2aff0a4fd0689523e6c17
2025-02-26
Published