CVE-2026-99481: Bluetooth: hci_vhci: Pin module for debugfs file operations

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hcivhci: Pin module for debugfs file operations

An open debugfs file retains its fileoperations pointer in the debugfs proxy state. However, forcesuspendfops, forcewakeupfops, aospcapablefops, and forcedevcoredumpfops have no .owner set to THISMODULE. As a result, fullproxyopenregular() calls fopsget() which succeeds without taking a reference to the hcivhci module.

When userspace opens any of these debugfs files and later closes the /dev/vhci file descriptor (triggering vhcirelease() and debugfs file removal), the open debugfs file descriptor remains valid in userspace. Because the module refcount was not incremented, the hcivhci module can be unloaded via deletemodule (rmmod hcivhci).

When the userspace process subsequently closes the debugfs file descriptor, fullproxyrelease() accesses the already unmapped fileoperations 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: errorcode(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP KASAN NOPTI RIP: 0010:fullproxyrelease+0x8e/0x140 Call Trace: <TASK> fput+0x39f/0xa60 fputclosesync+0xff/0x200 x64sysclose+0x8c/0xf0 dosyscall64+0xc3/0x590 entrySYSCALL64afterhwframe+0x76/0x7e </TASK> Modules linked in: ... [last unloaded: hcivhci(E)]

The issue was discovered via manual code audit of drivers/bluetooth/hcivhci.c and verified on a Linux 7.3-rc6 test VM with CONFIGBTVHCI=m by keeping a debugfs file open across controller teardown and module unload.

Set .owner = THISMODULE on all four fileoperations structures so that debugfs pins the module until all file descriptors are closed.

Affected Software

5 affected componentsFixes available
linux/kernel>=6.6.105<6.7
6.7
linux/kernel>=6.12.46<6.12.117
6.12.117
linux/kernel>=6.16.6<6.17
6.17
linux/kernel>=6.17.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.7
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.17
  4. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  5. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  6. Configuration

    Set .owner = THIS_MODULE on all four file_operations structures: force_suspend_fops, force_wakeup_fops, aosp_capable_fops, and force_devcoredump_fops.

    Bluetooth hci_vhci debugfs file_operations .owner = THIS_MODULE

Event History

Nov 19, 2026
CVE Published
via MITRE·02:43 PM
Data Sourced
via MITRE·02:43 PM
Description
Data Sourced
via OSV·02:43 PM
DescriptionAffected Software
Data Sourced
via NVD·03:18 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203