CVE-2022-49149rxrpc: Fix call timer start racing with call destruction
- 9.8CriticalCVSS base score
- 0.50%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 20 months later
· 20 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.50% · top 57% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 051360e51341cd17738d82c15a8226010c7cb7f6
- affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 8cbf4ae7a2833767d63114573e5f9a45740cc975
- affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 54df5a37f1d951ed27fd47bf9b15a42279582110
- affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 5e3c11144e557a9dbf9a2f6abe444689ef9d8aae
- affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 4a7f62f91933c8ae5308f9127fd8ea48188b6bc3
- affected 4.15
- unaffected < 4.15
- unaffected 5.10.110 – ≤ 5.10.*
- unaffected 5.15.33 – ≤ 5.15.*
- unaffected 5.16.19 – ≤ 5.16.*
- unaffected 5.17.2 – ≤ 5.17.*
- unaffected 5.18 – ≤ *
References
References5
- https://git.kernel.org/stable/c/051360e51341cd17738d82c15a8226010c7cb7f6 (opens in a new tab)
- https://git.kernel.org/stable/c/8cbf4ae7a2833767d63114573e5f9a45740cc975 (opens in a new tab)
- https://git.kernel.org/stable/c/54df5a37f1d951ed27fd47bf9b15a42279582110 (opens in a new tab)
- https://git.kernel.org/stable/c/5e3c11144e557a9dbf9a2f6abe444689ef9d8aae (opens in a new tab)
- https://git.kernel.org/stable/c/4a7f62f91933c8ae5308f9127fd8ea48188b6bc3 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55076 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49149)Record last updated .