Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26846: nvme-fc: do not wait in vain when unloading module

Noroxi assessment

Priority: Monitor (action score 17/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.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 085195aa90a924c79e35569bcdad860d764a8e17, 0bf567d6d9ffe09e059bbdfb4d07143cef42c75c, 4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2.

Low priority for now. Upgrade to Linux Linux 085195aa90a924c79e35569bcdad860d764a8e17, 0bf567d6d9ffe09e059bbdfb4d07143cef42c75c, 4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2 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-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too.

MediumCVSS 4.4 · v3.1—No exploit Fix available
Published
Apr 17, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2024-26846

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

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

  • debian debian linux10.0
  • linux linux kernel5.11 and later · before 5.15.150
  • linux linux kernel5.16 and later · before 6.1.80
  • linux linux kernelbefore 5.10.211
  • linux linux kernel6.7 and later · before 6.7.7
  • linux linux kernel6.2 and later · before 6.6.19
  • linux linux kernel6.8

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.3affected
    • 4c73cbdff1119d088ed16d63def59ad32b11b18f and later · before 4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2affected · git
    • 4c73cbdff1119d088ed16d63def59ad32b11b18f and later · before 0bf567d6d9ffe09e059bbdfb4d07143cef42c75caffected · git
    • 4c73cbdff1119d088ed16d63def59ad32b11b18f and later · before 085195aa90a924c79e35569bcdad860d764a8e17affected · git
    • 4c73cbdff1119d088ed16d63def59ad32b11b18f and later · before baa6b7eb8c66486bd64608adc63fe03b30d3c0b9affected · git
    • 4c73cbdff1119d088ed16d63def59ad32b11b18f and later · before c0882c366418bf9c19e1ba7f270fe377a9bf5d67affected · git
    • 4c73cbdff1119d088ed16d63def59ad32b11b18f and later · before 70fbfc47a392b98e5f8dba70c6efc6839205c982affected · git
    • before 5.3not affected · semver
    • 5.10.211 and later · up to and including 5.10.*not affected · semver
    • 5.15.150 and later · up to and including 5.15.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.57.1.el9_40:7.3.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-develbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-docbefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.57.1.el9_40:5.14.0-427.57.1.el9_4

+56

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2024-26844Apr 17, 2024 · block: Fix WARNING in _copy_from_iter
    22Monitor
  • ← EarlierCVE-2024-26845Apr 17, 2024 · scsi: target: core: Add TMF to tmr_list handling
    22Monitor
  • Later →CVE-2023-52644Apr 17, 2024 · wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled
    25Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Linux Linux085195aa90a924c79e35569bcdad860d764a8e17Vendor (CNA)
Linux Linux0bf567d6d9ffe09e059bbdfb4d07143cef42c75cVendor (CNA)
Linux Linux4f2c95015ec2a1899161be6c0bdaecedd5a7bfb2Vendor (CNA)
Linux Linux70fbfc47a392b98e5f8dba70c6efc6839205c982Vendor (CNA)
Linux Linuxbaa6b7eb8c66486bd64608adc63fe03b30d3c0b9Vendor (CNA)
Linux Linuxc0882c366418bf9c19e1ba7f270fe377a9bf5d67Vendor (CNA)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.57.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage 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.

No history yet (it accumulates with the daily EPSS job).

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.

  • CVE-2024-3581430 days apartswiotlb: Fix double-allocation of slots due to broken alignment handling
    35Monitor
  • CVE-2022-4864911 days apartmm/slab_common: fix possible double free of kmem_cache
    31Monitor
  • CVE-2024-2678213 days apartmptcp: fix double-free on socket dismantle
    31Monitor
  • CVE-2024-2679213 days apartbtrfs: fix double free of anonymous device after snapshot creation failure
    31Monitor
  • CVE-2024-2693214 days apartusb: typec: tcpm: fix double-free issue in tcpm_port_unregister_pd()
    31Monitor
  • CVE-2024-2739214 days apartnvme: host: fix double-free of struct nvme_id_ns in ns_update_nuse()
    31Monitor

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.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

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

nvd-secondary

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

  1. Fix✗ → ✓

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

References

Show all references (6 more)

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

All records