CVE-2024-41079
nvmet: always initialize cqe.result
Vexday Risk Score
3Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS —EPSS 0.3%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
29 Jul 2024Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
Affected products
Linux · LinuxWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://git.kernel.org/stable/c/0990e8a863645496b9e3f91cfcfd63cd95c80319https://git.kernel.org/stable/c/10967873b80742261527a071954be8b54f0f8e4dhttps://git.kernel.org/stable/c/30d35b24b7957922f81cfdaa66f2e1b1e9b9aed2https://git.kernel.org/stable/c/c6a2cf8b0764f3ba7d9bff58c8775a6d4476bb29https://git.kernel.org/stable/c/cd0c1b8e045a8d2785342b385cb2684d9b48e426https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html