nvmet: always initialize cqe.result
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.6%
exploitation probability
0.6%top 53% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
Linux · LinuxReferences
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