nvmet: fix return status of RMI log page on allocation failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 581d8bb556dd3e5567bcf322aa5e3e4b6a200c08, Kernel 9e136150ac55df4b7ea36e6110ffa39d08905f37 and Kernel ffd56ada81f975a33f1df447f1bec9090a818e98.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.13, >=5fd075cdaf3649000677d960fd9e45c08081b7e0 <581d8bb556dd3e5567bcf322aa5e3e4b6a200c08, >=5fd075cdaf3649000677d960fd9e45c08081b7e0 <9e136150ac55df4b7ea36e6110ffa39d08905f37, >=5fd075cdaf3649000677d960fd9e45c08081b7e0 <ffd56ada81f975a33f1df447f1bec9090a818e98 | 581d8bb556dd3e5567bcf322aa5e3e4b6a200c08, 9e136150ac55df4b7ea36e6110ffa39d08905f37, ffd56ada81f975a33f1df447f1bec9090a818e98 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket