PT-2026-152594
CVE-2026-99714
·
تاريخ النشر
2026-11-20
·
تاريخ التحديث
2026-11-20
الوصف من
الدرجة
N/A
غير متوفرلا تتوفر حاليًا تقييمات أو مقاييس للخطورة. سنحدّث المعلومات المقابلة في الصفحة فور توفرها.
In the Linux kernel, the following vulnerability has been resolved:
nvme: Do not drop the cdev reference twice when cdev device add() fails
Since commit 9952f3882ecb ("nvme: fix cdev lifetime"),
nvme add ns cdev() and nvme add ns head cdev() take a reference to the
namespace (or namespace head) before calling nvme cdev add(), to be
dropped by the char device's release, nvme cdev rel(), and drop it
themselves when nvme cdev add() fails. But when cdev device add()
fails, nvme cdev add() has already put the device, and nvme cdev rel()
has already dropped that reference: the caller drops it a second time.
With one allocation failure injected into cdev device add() for a
namespace on an NVMe over loop controller, deleting the controller
gives, with native multipath:
BUG: KASAN: slab-use-after-free in nvme put ns head+0x21/0x140
Write of size 4 at addr ff1100000a4ea078 by task init/1
nvme put ns head
nvme put ns
nvme remove namespaces
nvme do delete ctrl
nvme delete ctrl sync
nvme sysfs delete
Freed by task 1:
kfree
nvme ns remove
nvme remove namespaces
refcount t: underflow; use-after-free.
Take the reference in nvme cdev add() instead, right before
cdev device add(), and let the callers neither take nor drop it. Add
nvme is ns cdev() for the check that nvme cdev rel() and nvme cdev add()
now share.
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾