LiveActive security incident?Get immediate response
CVE Record

CVE-2024-41079: nvmet: always initialize cqe.result

In the Linux kernel, the following vulnerability has been resolved: nvmet: always initialize cqe.result The spec doesn't mandate that the first two double words (aka results) for the command queue entry need to be set to 0 when they are not used (not specified). Though, the target implemention returns 0 for TCP and FC but not for RDMA. Let's make RDMA behave the same and thus explicitly initializing the result field. This prevents leaking any data from the stack.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can leak small pieces of stack memory from systems acting as NVMe targets over RDMA. It is narrower than a general remote compromise, but exposed storage infrastructure should treat it as a confidentiality risk until patched.

Executive priority

Schedule remediation through normal high-priority kernel maintenance for exposed storage systems. Escalate if NVMe-over-RDMA target services are internet-facing or reachable by untrusted tenants.

Technical view

The NVMe target RDMA path did not always initialize cqe.result for unused command result fields. TCP and Fibre Channel paths returned zero, but RDMA could return uninitialized stack data. Kernel stable commits initialize the result field consistently.

Likely exposure

Exposure is most likely on Linux systems configured as NVMe-oF targets using RDMA on affected kernel branches. General Linux servers not providing NVMe target RDMA service are less likely to be affected.

Exploitation context

The source bundle shows no KEV listing and provides no cited evidence of active exploitation. Public details describe an information disclosure condition, not a complete compromise chain.

Researcher notes

Evidence supports an RDMA-specific uninitialized stack disclosure in nvmet command completion handling. The bundle does not provide CVSS, CWE, proof of exploitation, or a named workaround beyond applying kernel/vendor fixes.

Mitigation direction

  • Apply vendor kernel updates containing the stable fix commits.
  • Prioritize Linux storage hosts using NVMe target over RDMA.
  • Check Debian or distribution advisories for fixed package versions.
  • Limit NVMe-oF RDMA exposure to trusted networks where possible.

Validation and detection

  • Inventory Linux kernels against vendor fixed-version guidance.
  • Confirm whether NVMe target RDMA transport is enabled.
  • Verify updated kernel changelogs include the CVE or fix commits.
  • Review storage network exposure for untrusted RDMA access.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-41079 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa07b4970f464f13640e28e16dad6cfa33647cc99, a07b4970f464f13640e28e16dad6cfa33647cc99, a07b4970f464f13640e28e16dad6cfa33647cc99, a07b4970f464f13640e28e16dad6cfa33647cc99, a07b4970f464f13640e28e16dad6cfa33647cc99unaffected
LinuxLinux4.8, 0, 5.15.209, 6.1.101, 6.6.42, 6.9.11, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.