Secuno
ENNL
Book demo

CVE-2022-48985

Linux Kernel vulnerability

9.8 CRITICALEPSS 0.59%
  1. Published21 Oct 2024

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.

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≥ 5.15 < 5.15.83 · ≥ 5.16 < 6.0.13 · 6.1

Remediation

Fixed in
Linux Kernel≥ 5.15.83

References

Frequently asked

Is CVE-2022-48985 being actively exploited?

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

How severe is CVE-2022-48985?

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

Which products are affected by CVE-2022-48985?

Affected products include Linux Kernel.

How do I fix CVE-2022-48985?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2022-48985 against the real software inventory on every managed device, every day. 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 worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.