{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.117-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.3.3-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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:    \u003cTASK\u003e    __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    \u003c/TASK\u003e   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.",
  "id": "DEBIAN-CVE-2026-99481",
  "modified": "2026-11-20T04:47:37.419483710Z",
  "published": "2026-11-19T15:18:02.743Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-99481"
    }
  ],
  "upstream": [
    "CVE-2026-99481"
  ]
}