Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49149

rxrpc: Fix call timer start racing with call destruction

Critical9.8EPSS 0.50%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2022-49149, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium4.7CVSS: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 (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Weakness

Affected products

  • Linux · Linux

    • affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 051360e51341cd17738d82c15a8226010c7cb7f6
    • affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 8cbf4ae7a2833767d63114573e5f9a45740cc975
    • affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 54df5a37f1d951ed27fd47bf9b15a42279582110
    • affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 5e3c11144e557a9dbf9a2f6abe444689ef9d8aae
    • affected a158bdd3247b9656df36ba133235fff702e9fdc3 – < 4a7f62f91933c8ae5308f9127fd8ea48188b6bc3
  • Linux · Linux

    • 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 (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49149 badge
[![CVE-2022-49149](https://trackcve.app/badge/CVE-2022-49149.svg)](https://trackcve.app/cve/CVE-2022-49149)

Record last updated .