CVE-2022-48985
Last modified
CVE-2022-48985 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix race on per-CQ variable napi work_done After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be cleared, and another CPU can start napi thread and access per-CQ variable, cq->work_done. If the other thread (for example, from busy_poll) sets it to a value >= budget, this thread will continue to run when it should stop, and cause memory corruption and panic. To fix this issue, save the per-CQ work_done variable in a local variable before napi_complete_done(), so it won't be corrupted by a possible concurrent thread after napi_complete_done(). Also, add a flag bit to advertise to the NIC firmware: the NAPI work_done variable race is fixed, so the driver is able to reliably support features like busy_poll.. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix race on per-CQ variable napi work_done After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be cleared, and another CPU can start napi thread and access per-CQ variable, cq->work_done. If the other thread (for example, from busy_poll) sets it to a value >= budget, this thread will continue to run when it should stop, and cause memory corruption and panic. To fix this issue, save the per-CQ work_done variable in a local variable before napi_complete_done(), so it won't be corrupted by a possible concurrent thread after napi_complete_done(). Also, add a flag bit to advertise to the NIC firmware: the NAPI work_done variable race is fixed, so the driver is able to reliably support features like busy_poll.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.15, < 5.15.83 | — |
| Linux | Linux Kernel | >= 5.16, < 6.0.13 | — |
| Linux | Linux Kernel | 6.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-48985?
How severe is CVE-2022-48985?
How do I fix CVE-2022-48985?
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-4898In affected versions of Octopus Server the help sidebar can …5.4
- CVE-2022-48980In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-48981In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-48982In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48983In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48984In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48986In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48987In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48988In the Linux kernel, the following vulnerability has been re…7
- CVE-2022-48989In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2022-4899A vulnerability was found in zstd v1.4.10, where an attacker…7.5
- CVE-2022-48990In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2022-48985?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
