PT-2026-151728

CVE-2026-99517

·

تاريخ النشر

2026-11-19

·

تاريخ التحديث

2026-11-19

الوصف من

الدرجة
N/A
غير متوفر

لا تتوفر حاليًا تقييمات أو مقاييس للخطورة. سنحدّث المعلومات المقابلة في الصفحة فور توفرها.

In 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 &reg->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.
المورّدون
المنتجات المتأثرة
المعرّفات ذات الصلة
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾