All reports
Medium

kernel: nvmet: fix return status of RMI log page on allocation failure

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-90412

Probability of exploitation in the next 30 days: 0.20%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet: fix return status of RMI log page on allocation failure nvmet_execute_get_log_page_rmi() leaves 'status' holding NVME_SC_SUCCESS (set by the successful nvmet_req_find_ns() call) when the kzalloc() for the log buffer fails. It then jumps to the out label and completes the request with a success status, so the host is told the command succeeded while no data was transferred. Initialize 'status' to NVME_SC_INTERNAL, matching the smart log handler, so an allocation failure is reported as an internal error.

A flaw was found in the nvmet component of the Linux kernel. When processing an RMI log page, if memory allocation for the log buffer fails, the system incorrectly reports a successful operation to the host. This can lead to the host believing data was transferred when it was not, potentially causing data integrity issues or unexpected behavior.