CVE-2026-99517: nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()
In the Linux kernel, the following vulnerability has been resolved:
nvmet: fix use-after-free of the old registrant in nvmetprpreempt()
nvmetprpreempt() handles a preempt sent by the reservation holder by changing the reservation type with nvmetprupdateregattr(), unless the reservation is of an All Registrants type. For the holder that helper does not modify the registrant in place: it puts a copy on the registrant list, points pr->holder to the copy and passes the old registrant to kfreercu().
If the reservation type changed, nvmetprpreempt() then hands ®->hostid of that old registrant to nvmetprresvreleased(). Unless the reservation released notification is masked, that function takes subsys->lock and compares the host id against every controller of the subsystem. The caller only holds pr->prsem and is not in an RCU read-side critical section, so nothing keeps the old registrant alive while it is read.
The result is a read of 16 freed bytes that decides which controllers get the notification. Found by code inspection. kfreercu() defers the free, so it usually happens after the read; when the pending free is forced to run before the read, KASAN reports the host id as freed memory.
Pass the host id of the controller that sent the command instead. The registrant was looked up by that host id, and the controller outlives the request.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.61 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2