Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-42152: nvmet: fix a possible leak when destroy a ctrl during qp establishment

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.73% (FIRST EPSS); higher than 54.4% of all records.
  • 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 2f3c22b1d3d7e86712253244797a651998c141fa, 5502c1f1d0d7472706cc1f201aecf1c935d302d1, 818004f2a380420c19872171be716174d4985e33; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7.
  • Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 4.7.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2f3c22b1d3d7e86712253244797a651998c141fa, 5502c1f1d0d7472706cc1f201aecf1c935d302d1, 818004f2a380420c19872171be716174d4985e33; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7 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: nvmet: fix a possible leak when destroy a ctrl during qp establishment In nvmet_sq_destroy we capture sq->ctrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl->sqs and sq->ctrl (for nvme-loop primarily), and drop the final reference on the ctrl. However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But *before* kill_and_confirm of sq->ref (i.e. the admin connect managed to get an sq live reference). In this case, sq->ctrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl. Solve this by re-capturing the sq->ctrl after all inflight request has completed, where for sure sq->ctrl reference is final, and move forward based on that. This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Jul 30, 2024
Updated
Aug 5, 2026
EPSS
0.7% · 54th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

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

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
7.5
2.8 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.

Follow CVE-2024-42152

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

Affected versions

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

  • linux linux kernel4.8 and later · before 5.10.222
  • linux linux kernel5.11 and later · before 5.15.163
  • linux linux kernel5.16 and later · before 6.1.98
  • linux linux kernel6.2 and later · before 6.6.39
  • linux linux kernel6.7 and later · before 6.9.9
  • linux linux kernel6.10

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.6affected
    • 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a and later · before 2f3c22b1d3d7e86712253244797a651998c141faaffected · git
    • 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a and later · before b4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5affected · git
    • 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a and later · before 940a71f08ef153ef807f751310b0648d1fa5d0daaffected · git
    • 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a and later · before 5502c1f1d0d7472706cc1f201aecf1c935d302d1affected · git
    • 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a and later · before 818004f2a380420c19872171be716174d4985e33affected · git
    • 0f5be6a4ff7b3f8bf3db15f904e3e76797a43d9a and later · before c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4affected · git
    • before 5.6not affected · semver
    • 5.10.222 and later · up to and including 5.10.*not affected · semver
    • 5.15.163 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.98-16.1.98-1
Debian:13linuxbefore 6.9.9-16.9.9-1
Red Hat:rhel_eus:9.2::appstreambpftool-debuginfobefore 0:7.0.0-284.90.1.el9_20:7.0.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-develbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debuginfobefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-develbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-debuginfobefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-develbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfobefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-develbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-devel-matchedbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-docbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-tools-debuginfobefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-develbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-284.90.1.el9_20:5.14.0-284.90.1.el9_2

+54

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-42150Jul 30, 2024 · net: txgbe: remove separate irq request for MSI and INTx
    22Monitor
  • ← EarlierCVE-2024-42151Jul 30, 2024 · bpf: mark bpf_dummy_struct_ops.test_1 parameter as nullable
    22Monitor
  • Later →CVE-2024-42153Jul 30, 2024 · i2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr
    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 / packageFixed versionSource
Linux Linux2f3c22b1d3d7e86712253244797a651998c141faVendor (CNA)
Linux Linux5502c1f1d0d7472706cc1f201aecf1c935d302d1Vendor (CNA)
Linux Linux818004f2a380420c19872171be716174d4985e33Vendor (CNA)
Linux Linux940a71f08ef153ef807f751310b0648d1fa5d0daVendor (CNA)
Linux Linuxb4fed1443a6571d49c6ffe7d97af3bbe5ee6dff5Vendor (CNA)
Linux Linuxc758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4Vendor (CNA)
azl3 kernel 6.6.35.1-5 on Azure Linux 3.06.6.43.1-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.43.1-7 on Azure Linux 3.06.6.43.1-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.162.2-1 on CBL Mariner 2.05.15.164.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.162.2-1 on CBL-Mariner 2.05.15.164.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.164.1-1 on CBL Mariner 2.05.15.164.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.98-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-284.90.1.el9_2 · Red Hat:rhel_eus:9.2::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.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

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

nvd-primary

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