CVE-2024-41079: Linux kernel · nvmet: always initialize cqe.result
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 5.15.0-1112.119~20.04.1 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1112.119~20.04.1, 5.15.0-1117.126~20.04.1, 5.15.0-1117.126~20.04.2 +55
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-7156-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8575-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8576-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkeoppkg:deb/ubuntu/linux-gkeop?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2024-41079 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-41079 (opens in a new tab)
- git.kernel.org/linus/cd0c1b8e045a8d2785342b385cb2684d9b48e426 (opens in a new tab)
- git.kernel.org/stable/c/30d35b24b7957922f81cfdaa66f2e1b1e9b9aed2 (opens in a new tab)
- git.kernel.org/stable/c/10967873b80742261527a071954be8b54f0f8e4d (opens in a new tab)
- git.kernel.org/stable/c/0990e8a863645496b9e3f91cfcfd63cd95c80319 (opens in a new tab)
- git.kernel.org/stable/c/cd0c1b8e045a8d2785342b385cb2684d9b48e426 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-7156-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8575-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8576-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8575-2 (opens in a new tab)