Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2022-48985

A race condition in the Linux kernel's mana network driver could allow concurrent access to a per-CQ variable after NAPI completion, leading to memory corruption and a system panic. The flaw was fixed by saving the variable locally before completing NAPI work and adding a firmware flag to indicate the fix. Updating the kernel to a version that includes this patch resolves the issue.

publishedOct 21, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
45th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux systems using the mana network driver (affected kernel versions as listed in the CPE data).

02

Real-world impact

An attacker could trigger the race to cause memory corruption, resulting in a kernel panic and denial of service.

03

Why this severity

CVSS v3.1 base score 9.8 (Critical) due to network‑adjacent attack vector, low complexity, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 011. Obtain the latest Linux kernel update from your distribution that includes the fix for CVE-2022-48985 (the patch that resolves the mana driver race condition).
  2. 022. Install the kernel update using your system's package manager or update mechanism.
  3. 033. Reboot the system to load the patched kernel.

NVD-referenced vendor advisory (the NVD description states the vulnerability has been resolved in the Linux kernel).

05

Timeline

  1. Oct 21, 2024 · Oct 21, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →