CVE-2022-49149
Last modified
CVE-2022-49149 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.15.1, < 5.10.110 |
| Linux | Linux Kernel | >= 5.11, < 5.15.33 |
| Linux | Linux Kernel | >= 5.16, < 5.16.19 |
| Linux | Linux Kernel | >= 5.17, < 5.17.2 |
| Linux | Linux Kernel | 4.15 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-49149?
How severe is CVE-2022-49149?
How do I fix CVE-2022-49149?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49143Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-49144In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49145In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-49146In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49147In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49148In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4915Inappropriate implementation in URL Formatting in Google Chr…6.5
- CVE-2022-49150In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49151In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49152In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2022-49153In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49154In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49149?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
