CVE-2022-49149: Linux Kernel race condition (CVSS 9.8)

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Linux Kernel≥ 4.15.1 < 5.10.110 · ≥ 5.11 < 5.15.33 · ≥ 5.16 < 5.16.19 · ≥ 5.17 < 5.17.2

Remediation

Fixed in

Linux Kernel≥ 5.10.110

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2022-49149 being actively exploited?

CVE-2022-49149 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.48%.

How severe is CVE-2022-49149?

CVE-2022-49149 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.48% probability of exploitation.

Which products are affected by CVE-2022-49149?

Affected products include Linux Kernel.

How do I fix CVE-2022-49149?

Upgrade affected software to a fixed version, for example Linux Kernel 5.10.110 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2022-49149 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo