CVE-2026-99481
Bluetooth: hci_vhci: Pin module for debugfs file operations
What happened?
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: <TASK> __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 </TASK> 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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 1503756fffe76d5aea2371a4b8dee20c3577bcfd to < a82b3dec02bd42eedbc2733b092910f3b6bc4948; affected: 28010791193a4503f054e8d69a950ef815deb539 to < d5cc1f1333d47593fcc71b73d1fade556c8ece76; affected: 28010791193a4503f054e8d69a950ef815deb539 to < 19502449eeeafbf48ad1626cc356d178d549fcc0; affected: 28010791193a4503f054e8d69a950ef815deb539 to < 645ee6b176c958579cff1c783413d5cff65c8197; affected: bd75eba88e88d7b896b0c737b02a74a12afc235f; affected: 7cc08f2f127b9a66f46ea918e34353811a7cb378; affected: 6.12.46 to < 6.12.117; affected: 6.6.105 to < 6.7; affected: 6.16.6 to < 6.17 | See vendor advisory |
| LinuxLinux | affected: 6.17; unaffected: 0 to < 6.17; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99481
- https://git.kernel.org/stable/c/a82b3dec02bd42eedbc2733b092910f3b6bc4948
- https://git.kernel.org/stable/c/d5cc1f1333d47593fcc71b73d1fade556c8ece76
- https://git.kernel.org/stable/c/19502449eeeafbf48ad1626cc356d178d549fcc0
- https://git.kernel.org/stable/c/645ee6b176c958579cff1c783413d5cff65c8197