CVE-2022-49149
published 2025-02-26CVE-2022-49149: In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has a timer…
PriorityP416medium4.7CVSS 3.1
AVLACHPRLUINSUCNINAH
EPSS
0.47%
38.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix call timer start racing with call destruction
The rxrpc_call struct has a timer used to handle various timed events
relating to a call. This timer can get started from the packet input
routines that are run in softirq mode with just the RCU read lock held.
Unfortunately, because only the RCU read lock is held - and neither ref or
other lock is taken - the call can start getting destroyed at the same time
a packet comes in addressed to that call. This causes the timer - which
was already stopped - to get restarted. Later, the timer dispatch code may
then oops if the timer got deallocated first.
Fix this by trying to take a ref on the rxrpc_call struct and, if
successful, passing that ref along to the timer. If the timer was already
running, the ref is discarded.
The timer completion routine can then pass the ref along to the call's work
item when it queues it. If the timer or work item where already
queued/running, the extra ref is discarded.
Affected
24 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 | >= a158bdd3247b9656df36ba133235fff702e9fdc3 < 051360e51341cd17738d82c15a8226010c7cb7f6 | 051360e51341cd17738d82c15a8226010c7cb7f6 |
| linux | linux | >= a158bdd3247b9656df36ba133235fff702e9fdc3 < 8cbf4ae7a2833767d63114573e5f9a45740cc975 | 8cbf4ae7a2833767d63114573e5f9a45740cc975 |
| linux | linux | >= a158bdd3247b9656df36ba133235fff702e9fdc3 < 54df5a37f1d951ed27fd47bf9b15a42279582110 | 54df5a37f1d951ed27fd47bf9b15a42279582110 |
| linux | linux | >= a158bdd3247b9656df36ba133235fff702e9fdc3 < 5e3c11144e557a9dbf9a2f6abe444689ef9d8aae | 5e3c11144e557a9dbf9a2f6abe444689ef9d8aae |
| linux | linux | >= a158bdd3247b9656df36ba133235fff702e9fdc3 < 4a7f62f91933c8ae5308f9127fd8ea48188b6bc3 | 4a7f62f91933c8ae5308f9127fd8ea48188b6bc3 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| 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 | >= 4.15.1 < 5.10.110 | 5.10.110 |
| linux | linux_kernel | >= 5.11 < 5.15.33 | 5.15.33 |
| linux | linux_kernel | >= 5.16 < 5.16.19 | 5.16.19 |
| linux | linux_kernel | >= 5.17 < 5.17.2 | 5.17.2 |
CVSS provenance
nvdv3.14.7MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
osv4.7MEDIUM
vendor_debian4.7MEDIUM
vendor_redhat4.7MEDIUM
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: rxrpc: Fix call timer start racing with call destruction
vendor_redhat·2025-02-26·CVSS 4.7
CVE-2022-49149 [MEDIUM] CWE-362 kernel: rxrpc: Fix call timer start racing with call destruction
kernel: rxrpc: Fix call timer start racing with call destruction
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix call timer start racing with call destruction
The rxrpc_call struct has a timer used to handle various timed events
relating to a call. This timer can get started from the packet input
routines that are run in softirq mode with just the RCU read lock held.
Unfortunately, because only the RCU read lock is held - and neither ref or
other lock is taken - the call can start getting destroyed at the same time
a packet comes in addressed to that call. This causes the timer - which
was already stopped - to get restarted. Later, the timer dispatch code may
then oops if the timer got deallocated first.
Fix this by trying to take a ref on the rxrpc_call str
Debian
CVE-2022-49149: linux - In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix ...
vendor_debian·2022·CVSS 4.7
CVE-2022-49149 [MEDIUM] CVE-2022-49149: linux - In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix ...
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has a timer used to handle various timed events relating to a call. This timer can get started from the packet input routines that are run in softirq mode with just the RCU read lock held. Unfortunately, because only the RCU read lock is held - and neither ref or other lock is taken - the call can start getting destroyed at the same time a packet comes in addressed to that call. This causes the timer - which was already stopped - to get restarted. Later, the timer dispatch code may then oops if the timer got deallocated first. Fix this by trying to take a ref on the rxrpc_call struct and, if successful, passing that ref along to the timer. If th
GHSA
GHSA-g36j-w8h6-jr97: In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix call timer start racing with call destruction
The rxrpc_call struct h
ghsa_unreviewed·2025-09-23
CVE-2022-49149 [MEDIUM] CWE-362 GHSA-g36j-w8h6-jr97: In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix call timer start racing with call destruction
The rxrpc_call struct h
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix call timer start racing with call destruction
The rxrpc_call struct has a timer used to handle various timed events
relating to a call. This timer can get started from the packet input
routines that are run in softirq mode with just the RCU read lock held.
Unfortunately, because only the RCU read lock is held - and neither ref or
other lock is taken - the call can start getting destroyed at the same time
a packet comes in addressed to that call. This causes the timer - which
was already stopped - to get restarted. Later, the timer dispatch code may
then oops if the timer got deallocated first.
Fix this by trying to take a ref on the rxrpc_call struct and, if
successful, passing that ref along to the timer. If
OSV
CVE-2022-49149: In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has
osv·2025-02-26·CVSS 4.7
CVE-2022-49149 [MEDIUM] CVE-2022-49149: In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has a timer used to handle various timed events relating to a call. This timer can get started from the packet input routines that are run in softirq mode with just the RCU read lock held. Unfortunately, because only the RCU read lock is held - and neither ref or other lock is taken - the call can start getting destroyed at the same time a packet comes in addressed to that call. This causes the timer - which was already stopped - to get restarted. Later, the timer dispatch code may then oops if the timer got deallocated first. Fix this by trying to take a ref on the rxrpc_call struct and, if successful, passing that ref along to the timer. If th
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/051360e51341cd17738d82c15a8226010c7cb7f6https://git.kernel.org/stable/c/4a7f62f91933c8ae5308f9127fd8ea48188b6bc3https://git.kernel.org/stable/c/54df5a37f1d951ed27fd47bf9b15a42279582110https://git.kernel.org/stable/c/5e3c11144e557a9dbf9a2f6abe444689ef9d8aaehttps://git.kernel.org/stable/c/8cbf4ae7a2833767d63114573e5f9a45740cc975
2025-02-26
Published