BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49149High confidence

rxrpc: Fix call timer start racing with call destruction

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 110 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.50% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 110 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 4 Nov 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-49149 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: rxrpc: Fix call timer start racing with call destruction
109 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • bpftool as a component of Red Hat Enterprise Linux 9
  • kernel as a component of Red Hat Enterprise Linux 9
  • kernel-64k as a component of Red Hat Enterprise Linux 9
  • kernel-64k-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9
Summary
CVE-2022-49149 is a vulnerability in the Linux kernel's RxRPC (Remote Execution RPC) subsystem, which is used for remote procedure calls over the network. The issue stems from a race condition in the handling of call timers within the rxrpc_call structure. Specifically, when packet input routines operate in softirq mode with only a Read-Copy-Update (RCU) read lock held, a timer associated with a call can be started while the call is simultaneously being destroyed. This situation can lead to the timer being restarted after it has been deallocated, resulting in a null pointer dereference and potentially causing a system crash.
Remediation
Affected
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-55076

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 110 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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

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.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-362
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2022-55076Official EUVD mapping

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.

Official EUVD record ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250305Security Bulletin 5 March 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 March 2025, published on 5 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1537Avis du CERT-FR

curity/notices/USN-9035-1 Référence CVE CVE-2017-9986 https://www.cve.org/CVERecord?id=CVE-2017-9986 Référence CVE CVE-2021-47633 https://www.cve.org/CVERecord?id=CVE-2021-47633 Référence CVE CVE-2022-1205 https://www.cve.org/CVERecord?id=CVE-2022-1205 Référence CVE CVE-2022-23036 https://www.cve.org/CVERecord?id=CVE-2022-23036 Référence CVE CVE-2022-23037 https://www.cve.org/CVERecord?id=CVE-2022-23037 Référence CVE CVE-2022-3114 https://www.cve.org/CVERecord?id=CVE-2022-3114 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49149 https://www.cve.org/CVERecord?id=CVE-2022-49149 Référence CVE CVE-2022-49170 https://www.cve.org/CVERecord?id=CVE-2022-49170 Référence CVE CVE-2022-49234 https://www.cve.org/CVERecord?id=CVE-2022-49234 Référence CVE CVE-2022-49359 https://www.cve.org/CVERecord?id=CVE-2022-49359 Référence CVE CVE-2022-49562 https://www.cve.org/CVERecord?id=CVE-2022-49562 Référence CVE CVE-2022-49651 https://www.cve.org/CVERecord?id=CVE-2022-49651 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-50071 https://www.cve.org/CVERecord?id=CVE-2022-50071 Référence CVE CVE-2022-50303 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1469Avis du CERT-FR

8967-1 du 03 novembre 2026 https://ubuntu.com/security/notices/USN-8967-1 Bulletin de sécurité Ubuntu USN-8968-1 du 03 novembre 2026 https://ubuntu.com/security/notices/USN-8968-1 Référence CVE CVE-2021-28714 https://www.cve.org/CVERecord?id=CVE-2021-28714 Référence CVE CVE-2021-3640 https://www.cve.org/CVERecord?id=CVE-2021-3640 Référence CVE CVE-2022-1205 https://www.cve.org/CVERecord?id=CVE-2022-1205 Référence CVE CVE-2022-3114 https://www.cve.org/CVERecord?id=CVE-2022-3114 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49082 https://www.cve.org/CVERecord?id=CVE-2022-49082 Référence CVE CVE-2022-49149 https://www.cve.org/CVERecord?id=CVE-2022-49149 Référence CVE CVE-2022-49170 https://www.cve.org/CVERecord?id=CVE-2022-49170 Référence CVE CVE-2022-49182 https://www.cve.org/CVERecord?id=CVE-2022-49182 Référence CVE CVE-2022-49201 https://www.cve.org/CVERecord?id=CVE-2022-49201 Référence CVE CVE-2022-49234 https://www.cve.org/CVERecord?id=CVE-2022-49234 Référence CVE CVE-2022-49359 https://www.cve.org/CVERecord?id=CVE-2022-49359 Référence CVE CVE-2022-49562 https://www.cve.org/CVERecord?id=CVE-2022-49562 Référence CVE CVE-2022-49651 https://www.cve.org/CVERecord?id=CVE-2022-49651 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1333Avis du CERT-FR

CVERecord?id=CVE-2018-13100 Référence CVE CVE-2018-5848 https://www.cve.org/CVERecord?id=CVE-2018-5848 Référence CVE CVE-2021-3752 https://www.cve.org/CVERecord?id=CVE-2021-3752 Référence CVE CVE-2021-39634 https://www.cve.org/CVERecord?id=CVE-2021-39634 Référence CVE CVE-2021-4083 https://www.cve.org/CVERecord?id=CVE-2021-4083 Référence CVE CVE-2022-24448 https://www.cve.org/CVERecord?id=CVE-2022-24448 Référence CVE CVE-2022-3114 https://www.cve.org/CVERecord?id=CVE-2022-3114 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49149 https://www.cve.org/CVERecord?id=CVE-2022-49149 Référence CVE CVE-2022-49170 https://www.cve.org/CVERecord?id=CVE-2022-49170 Référence CVE CVE-2022-49182 https://www.cve.org/CVERecord?id=CVE-2022-49182 Référence CVE CVE-2022-49201 https://www.cve.org/CVERecord?id=CVE-2022-49201 Référence CVE CVE-2023-20585 https://www.cve.org/CVERecord?id=CVE-2023-20585 Référence CVE CVE-2023-54125 https://www.cve.org/CVERecord?id=CVE-2023-54125 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2024-53187 https://www.cve.org/CVERecord?id=CVE-2024-53187 Référence CVE CVE-2024-53194 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026307Linux の Linux Kernel における競合状態に関する脆弱性

Linux の Linux Kernel には、競合状態に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.15, 5.10.110 ≤ 5.10.*, 5.15.33 ≤ 5.15.*, 5.16.19 ≤ 5.16.*, 5.17.2 ≤ 5.17.*, 5.18 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 15 Oct 2026, 21:21 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-55076
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    a158bdd3247b9656df36ba133235fff702e9fdc3 < 051360e51341cd17738d82c15a8226010c7cb7f6; a158bdd3247b9656df36ba133235fff702e9fdc3 < 8cbf4ae7a2833767d63114573e5f9a45740cc975; a158bdd3247b9656df36ba133235fff702e9fdc3 < 54df5a37f1d951ed27fd47bf9b15a42279582110; a158bdd3247b9656df36ba133235fff702e9fdc3 < 5e3c11144e557a9dbf9a2f6abe444689ef9d8aae; a158bdd3247b9656df36ba133235fff702e9fdc3 < 4a7f62f91933c8ae5308f9127fd8ea48188b6bc3; 4.15 · Fixed: < 4.15; 5.10.110 ≤ 5.10.*; 5.15.33 ≤ 5.15.*; 5.16.19 ≤ 5.16.*; 5.17.2 ≤ 5.17.*; 5.18 ≤ *
    After
    Linux: a158bdd3247b9656df36ba133235fff702e9fdc3 < 051360e51341cd17738d82c15a8226010c7cb7f6, a158bdd3247b9656df36ba133235fff702e9fdc3 < 8cbf4ae7a2833767d63114573e5f9a45740cc975, a158bdd3247b9656df36ba133235fff702e9fdc3 < 54df5a37f1d951ed27fd47bf9b15a42279582110, a158bdd3247b9656df36ba133235fff702e9fdc3 < 5e3c11144e557a9dbf9a2f6abe444689ef9d8aae, a158bdd3247b9656df36ba133235fff702e9fdc3 < 4a7f62f91933c8ae5308f9127fd8ea48188b6bc3, 4.15 · Fixed: Linux: < 4.15, 5.10.110 ≤ 5.10.*, 5.15.33 ≤ 5.15.*, 5.16.19 ≤ 5.16.*, 5.17.2 ≤ 5.17.*, 5.18 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49149 · cve.blacktree.nl