Skip to content
Threat Brief

← All advisories

CVE-2026-99779

Severity unknownNo known exploitationFix available

net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable()

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 8% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom a3be076dc174d9022a71a12554feb4c97b5c4d5c before 52544826f345280beb13d150c3bc41e61353fa0c52544826f345280beb13d150c3bc41e61353fa0cCVE Program
LinuxLinuxfrom a3be076dc174d9022a71a12554feb4c97b5c4d5c before 277167375d269e411e2c5ce79527ff3ebf57a0bc277167375d269e411e2c5ce79527ff3ebf57a0bcCVE Program
LinuxLinuxfrom a3be076dc174d9022a71a12554feb4c97b5c4d5c before cd1988cf723c2eae87112b198bf90b0aebfeaf31cd1988cf723c2eae87112b198bf90b0aebfeaf31CVE Program
LinuxLinuxfrom a3be076dc174d9022a71a12554feb4c97b5c4d5c before 2d2e942cd9a8fc1f11e3e8e0340a0bb4ec1e9b9c2d2e942cd9a8fc1f11e3e8e0340a0bb4ec1e9b9cCVE Program
LinuxLinux6.12Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references