PT-2026-151766

CVE-2026-99555

·

تاريخ النشر

2026-11-19

·

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

2026-11-19

الوصف من

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

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

In the Linux kernel, the following vulnerability has been resolved:
media: usbtv: fix null-pointer dereference on disconnect
A null-pointer dereference can occur in usb make path() when called from usbtv querycap() (and other ioctl handlers) during device disconnection.
Oops: general protection fault, probably for non-canonical address 0xdffffc000000000a: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000050-0x0000000000000057] RIP: 0010:usb make path include/linux/usb.h:985 [inline] RIP: 0010:usbtv querycap+0x9c/0x100 drivers/media/usb/usbtv/usbtv-video.c:612 ... Call Trace: v4l querycap+0x236/0x470 drivers/media/v4l2-core/v4l2-ioctl.c:1106 video do ioctl+0x8af/0xc70 drivers/media/v4l2-core/v4l2-ioctl.c:3133 video usercopy+0x860/0x1430 drivers/media/v4l2-core/v4l2-ioctl.c:3475 v4l2 ioctl+0x18d/0x1e0 drivers/media/v4l2-core/v4l2-dev.c:366 vfs ioctl fs/ioctl.c:51 [inline] do sys ioctl fs/ioctl.c:597 [inline] se sys ioctl+0xfc/0x170 fs/ioctl.c:583 do syscall x64 arch/x86/entry/syscall 64.c:63 [inline] do syscall 64+0x174/0x580 arch/x86/entry/syscall 64.c:94
This happens due to a race condition between the USB device disconnect routine (usbtv disconnect()) and V4L2 ioctls. When the device is disconnected, usbtv disconnect() sets usbtv->udev = NULL without holding the usbtv->v4l2 lock mutex. Concurrently, an ioctl handler like usbtv querycap() can be executing under the v4l2 lock and attempt to use usbtv->udev, leading to a crash.
To fix this, move the usbtv->udev = NULL assignment into usbtv video free() and protect it with mutex lock(&usbtv->v4l2 lock). This ensures that no non-queue ioctl handler can run concurrently with the pointer being nullified. If an ioctl is already running, the mutex will block the disconnect path until the ioctl finishes. If an ioctl is blocked waiting for the lock, it will acquire it after the disconnect routine releases it, but will then check video is registered() (which was cleared by vb2 video unregister device()) and safely return -ENODEV.
Acquiring v4l2 lock after vb2 video unregister device() avoids reintroducing a historical deadlock issue, and usbtv audio free() remains safe as it is called before usbtv video free().
المورّدون
المنتجات المتأثرة
المعرّفات ذات الصلة
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾