NVD / CVE Program· CNA Linux

CVE-2022-49003: nvme: fix SRCU protection of nvme_ns_head list

Noroxi assessment

Priority: Monitor (action score 18/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.61% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Linux Linux 5b566d09ab1b975566a53f9c5466ee260d087582, 787d81d4eb150e443e5d1276c6e8f03cfecc2302, 899d2a05dc14733cfba6224083c6b0dd5a738590.
Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 4.7.

Low priority for now. Upgrade to Linux Linux 5b566d09ab1b975566a53f9c5466ee260d087582, 787d81d4eb150e443e5d1276c6e8f03cfecc2302, 899d2a05dc14733cfba6224083c6b0dd5a738590 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nvme: fix SRCU protection of nvme_ns_head list Walking the nvme_ns_head siblings list is protected by the head's srcu in nvme_ns_head_submit_bio() but not nvme_mpath_revalidate_paths(). Removing namespaces from the list also fails to synchronize the srcu. Concurrent scan work can therefore cause use-after-frees. Hold the head's srcu lock in nvme_mpath_revalidate_paths() and synchronize with the srcu, not the global RCU, in nvme_ns_remove(). Observed the following panic when making NVMe/RDMA connections with native multipath on the Rocky Linux 8.6 kernel (it seems the upstream kernel has the same race condition). Disassembly shows the faulting instruction is cmp 0x50(%rdx),%rcx; computing capacity != get_capacity(ns->disk). Address 0x50 is dereferenced because ns->disk is NULL. The NULL disk appears to be the result of concurrent scan work freeing the namespace (note the log line in the middle of the panic). [37314.206036] BUG: unable to handle kernel NULL pointer dereference at 0000000000000050 [37314.206036] nvme0n3: detected capacity change from 0 to 11811160064 [37314.299753] PGD 0 P4D 0 [37314.299756] Oops: 0000 [#1] SMP PTI [37314.299759] CPU: 29 PID: 322046 Comm: kworker/u98:3 Kdump: loaded Tainted: G W X --------- - - 4.18.0-372.32.1.el8test86.x86_64 #1 [37314.299762] Hardware name: Dell Inc. PowerEdge R720/0JP31P, BIOS 2.7.0 05/23/2018 [37314.299763] Workqueue: nvme-wq nvme_scan_work [nvme_core] [37314.299783] RIP: 0010:nvme_mpath_revalidate_paths+0x26/0xb0 [nvme_core] [37314.299790] Code: 1f 44 00 00 66 66 66 66 90 55 53 48 8b 5f 50 48 8b 83 c8 c9 00 00 48 8b 13 48 8b 48 50 48 39 d3 74 20 48 8d 42 d0 48 8b 50 20 <48> 3b 4a 50 74 05 f0 80 60 70 ef 48 8b 50 30 48 8d 42 d0 48 39 d3 [37315.058803] RSP: 0018:ffffabe28f913d10 EFLAGS: 00010202 [37315.121316] RAX: ffff927a077da800 RBX: ffff92991dd70000 RCX: 0000000001600000 [37315.206704] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff92991b719800 [37315.292106] RBP: ffff929a6b70c000 R08: 000000010234cd4a R09: c0000000ffff7fff [37315.377501] R10: 0000000000000001 R11: ffffabe28f913a30 R12: 0000000000000000 [37315.462889] R13: ffff92992716600c R14: ffff929964e6e030 R15: ffff92991dd70000 [37315.548286] FS: 0000000000000000(0000) GS:ffff92b87fb80000(0000) knlGS:0000000000000000 [37315.645111] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [37315.713871] CR2: 0000000000000050 CR3: 0000002208810006 CR4: 00000000000606e0 [37315.799267] Call Trace: [37315.828515] nvme_update_ns_info+0x1ac/0x250 [nvme_core] [37315.892075] nvme_validate_or_alloc_ns+0x2ff/0xa00 [nvme_core] [37315.961871] ? __blk_mq_free_request+0x6b/0x90 [37316.015021] nvme_scan_work+0x151/0x240 [nvme_core] [37316.073371] process_one_work+0x1a7/0x360 [37316.121318] ? create_worker+0x1a0/0x1a0 [37316.168227] worker_thread+0x30/0x390 [37316.212024] ? create_worker+0x1a0/0x1a0 [37316.258939] kthread+0x10a/0x120 [37316.297557] ? set_kthread_struct+0x50/0x50 [37316.347590] ret_from_fork+0x35/0x40 [37316.390360] Modules linked in: nvme_rdma nvme_tcp(X) nvme_fabrics nvme_core netconsole iscsi_tcp libiscsi_tcp dm_queue_length dm_service_time nf_conntrack_netlink br_netfilter bridge stp llc overlay nft_chain_nat ipt_MASQUERADE nf_nat xt_addrtype xt_CT nft_counter xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_comment xt_multiport nft_compat nf_tables libcrc32c nfnetlink dm_multipath tg3 rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm intel_rapl_msr iTCO_wdt iTCO_vendor_support dcdbas intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm irqbypass crct10dif_pclmul crc32_pclmul mlx5_ib ghash_clmulni_intel ib_uverbs rapl intel_cstate intel_uncore ib_core ipmi_si joydev mei_me pcspkr ipmi_devintf mei lpc_ich wmi ipmi_msghandler acpi_power_meter ex ---truncated---

MediumCVSS 4.7 · v3.1—No exploit Fix available

Published: Oct 21, 2024
Updated: Aug 5, 2026
EPSS: 0.6% · 49th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 18 / 40 · 4.7 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 4.7
CNA · Linux: 9.8; 5.1 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

ProductVersion

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.15 and later · before 5.15.82
linux linux kernel5.16 and later · before 6.0.12
linux linux kernel6.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.15affected
- e7d65803e2bb5bc739548b67a5fc72c626cf7e3b and later · before 787d81d4eb150e443e5d1276c6e8f03cfecc2302affected · git
- e7d65803e2bb5bc739548b67a5fc72c626cf7e3b and later · before 5b566d09ab1b975566a53f9c5466ee260d087582affected · git
- e7d65803e2bb5bc739548b67a5fc72c626cf7e3b and later · before 899d2a05dc14733cfba6224083c6b0dd5a738590affected · git
- before 5.15not affected · semver
- 5.15.82 and later · up to and including 5.15.*not affected · semver
- 6.0.12 and later · up to and including 6.0.*not affected · semver
- 6.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.0.12-1	6.0.12-1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	kernel-default-base	before 5.3.18-150200.24.209.1.150200.9.109.1	5.3.18-150200.24.209.1.150200.9.109.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	kernel-docs	before 5.3.18-150200.24.209.2	5.3.18-150200.24.209.2
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	kernel-obs-build	before 5.3.18-150200.24.209.1	5.3.18-150200.24.209.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	kernel-preempt	before 5.3.18-150200.24.209.1	5.3.18-150200.24.209.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	kernel-source	before 5.3.18-150200.24.209.1	5.3.18-150200.24.209.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	kernel-syms	before 5.3.18-150200.24.209.1	5.3.18-150200.24.209.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	kernel-64kb	before 5.3.18-150300.59.182.1	5.3.18-150300.59.182.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	kernel-default-base	before 5.3.18-150300.59.182.1.150300.18.107.1	5.3.18-150300.59.182.1.150300.18.107.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	kernel-docs	before 5.3.18-150300.59.182.2	5.3.18-150300.59.182.2
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	kernel-obs-build	before 5.3.18-150300.59.182.1	5.3.18-150300.59.182.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	kernel-preempt	before 5.3.18-150300.59.182.1	5.3.18-150300.59.182.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	kernel-source	before 5.3.18-150300.59.182.1	5.3.18-150300.59.182.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	kernel-syms	before 5.3.18-150300.59.182.1	5.3.18-150300.59.182.1
SUSE:Linux Enterprise Live Patching 15 SP2	kernel-default	before 5.3.18-150200.24.209.1	5.3.18-150200.24.209.1
SUSE:Linux Enterprise Live Patching 15 SP2	kernel-livepatch-SLE15-SP2_Update_54	before 1-150200.5.3.1	1-150200.5.3.1
SUSE:Linux Enterprise Live Patching 15 SP3	kernel-default	before 5.3.18-150300.59.182.1	5.3.18-150300.59.182.1
SUSE:Linux Enterprise Live Patching 15 SP3	kernel-livepatch-SLE15-SP3_Update_50	before 1-150300.7.3.1	1-150300.7.3.1
SUSE:Linux Enterprise Micro 5.1	kernel-rt	before 5.3.18-150300.191.1	5.3.18-150300.191.1
SUSE:Linux Enterprise Micro 5.1	kernel-source-rt	before 5.3.18-150300.191.1	5.3.18-150300.191.1
SUSE:Linux Enterprise Server 15 SP3-LTSS	kernel-zfcpdump	before 5.3.18-150300.59.182.1	5.3.18-150300.59.182.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now
CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
83Now

Published before and after this one in the same product

← EarlierCVE-2022-49001Oct 21, 2024 · riscv: fix race when vmap stack overflow
28Monitor
← EarlierCVE-2022-49002Oct 21, 2024 · iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init()
22Monitor
Later →CVE-2022-49004Oct 21, 2024 · riscv: Sync efi page table's kernel mappings before switching
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	5b566d09ab1b975566a53f9c5466ee260d087582	Vendor (CNA)
Linux Linux	787d81d4eb150e443e5d1276c6e8f03cfecc2302	Vendor (CNA)
Linux Linux	899d2a05dc14733cfba6224083c6b0dd5a738590	Vendor (CNA)
debian:linux	6.0.12-1 · Debian:12	Package registry (OSV)
suse:kernel-64kb	5.3.18-150300.59.182.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS	Package registry (OSV)
suse:kernel-default	5.3.18-150200.24.209.1 · SUSE:Linux Enterprise Live Patching 15 SP2	Package registry (OSV)
suse:kernel-default-base	5.3.18-150200.24.209.1.150200.9.109.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	Package registry (OSV)
suse:kernel-docs	5.3.18-150200.24.209.2 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	Package registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_54	1-150200.5.3.1 · SUSE:Linux Enterprise Live Patching 15 SP2	Package registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_50	1-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3	Package registry (OSV)
suse:kernel-obs-build	5.3.18-150200.24.209.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	Package registry (OSV)
suse:kernel-preempt	5.3.18-150200.24.209.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	Package registry (OSV)
suse:kernel-rt	5.3.18-150300.191.1 · SUSE:Linux Enterprise Micro 5.1	Package registry (OSV)
suse:kernel-source	5.3.18-150200.24.209.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	Package registry (OSV)
suse:kernel-source-rt	5.3.18-150300.191.1 · SUSE:Linux Enterprise Micro 5.1	Package registry (OSV)
suse:kernel-syms	5.3.18-150200.24.209.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/5b566d09ab1b975566a53f9c5466ee260d087582

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records