PT-2026-151692
CVE-2026-99481
·
تاريخ النشر
2026-11-19
·
تاريخ التحديث
2026-11-19
الوصف من
الدرجة
N/A
غير متوفرلا تتوفر حاليًا تقييمات أو مقاييس للخطورة. سنحدّث المعلومات المقابلة في الصفحة فور توفرها.
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci vhci: Pin module for debugfs file operations
An open debugfs file retains its file operations pointer in the
debugfs proxy state. However, force suspend fops, force wakeup fops,
aosp capable fops, and force devcoredump fops have no .owner set to
THIS MODULE. As a result, full proxy open regular() calls fops get()
which succeeds without taking a reference to the hci vhci module.
When userspace opens any of these debugfs files and later closes
the /dev/vhci file descriptor (triggering vhci release() and
debugfs file removal), the open debugfs file descriptor remains valid
in userspace. Because the module refcount was not incremented,
the hci vhci module can be unloaded via delete module (rmmod hci vhci).
When the userspace process subsequently closes the debugfs file
descriptor, full proxy release() accesses the already unmapped
file operations structure, resulting in a kernel page fault / oops:
BUG: unable to handle page fault for address: fffffbfff846f18b
#PF: supervisor read access in kernel mode
#PF: error code(0x0000) - not-present page
Oops: Oops: 0000 [#1] SMP KASAN NOPTI
RIP: 0010:full proxy release+0x8e/0x140
Call Trace:
fput+0x39f/0xa60
fput close sync+0xff/0x200
x64 sys close+0x8c/0xf0
do syscall 64+0xc3/0x590
entry SYSCALL 64 after hwframe+0x76/0x7e
Modules linked in: ... [last unloaded: hci vhci(E)]
The issue was discovered via manual code audit of
drivers/bluetooth/hci vhci.c and verified on a Linux 7.3-rc6 test VM
with CONFIG BT VHCI=m by keeping a debugfs file open across controller
teardown and module unload.
Set .owner = THIS MODULE on all four file operations structures so that
debugfs pins the module until all file descriptors are closed.
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾