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

CVE-2022-49003

A critical bug in the Linux kernel’s NVMe driver can cause the system to crash when NVMe devices are scanned concurrently. The flaw allows a use‑after‑free that leads to a kernel panic, disrupting service. It is a severe issue that can affect any Linux system running an unpatched kernel.

publishedOct 21, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
46th 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 kernel, including all current releases such as 6.1 and earlier versions that have not applied the NVMe SRCU protection fix. System administrators and users of unpatched Linux distributions are at risk.

02

Real-world impact

An attacker could trigger a kernel crash, causing a denial of service and potentially exposing the system to further compromise if the crash is leveraged in a larger attack chain.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability can be exploited remotely (AV:N) with no authentication (PR:N) and no user interaction (UI:N). It results in complete loss of confidentiality, integrity, and availability, making it a critical threat.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the nvme SRCU protection fix.
  2. 02Restart the system to load the updated kernel.

NVD-referenced vendor advisory

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 →