Linux kernel use-after-free in NVMe target reservation preemption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.617.3.27.4-rc1In the Linux kernel, the following vulnerability has been resolved:
nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()
nvmet_pr_preempt() handles a preempt sent by the reservation holder by changing the reservation type with nvmet_pr_update_reg_attr(), 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 kfree_rcu().
If the reservation type changed, nvmet_pr_preempt() then hands ®->hostid of that old registrant to nvmet_pr_resv_released(). 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->pr_sem 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. kfree_rcu() 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.
From the CVE record · Linux
The Linux kernel's nvmet_pr_preempt() can read a freed registrant's host ID when a reservation holder sends a preempt command that changes the reservation type. If reservation-release notifications are not masked, the freed host ID can affect which controllers receive a notification. The input does not specify an exploitable impact beyond this use-after-free read.
Engineers running the Linux kernel with nvmet should check their deployments; affected versions are not specified.