# CVE-2026-43432: usb: xhci: Fix memory leak in xhci_disable_slot()

Status: published. Published: 2026-05-08. Updated: 2026-11-06.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ fee8be5bde562d4f5f9a100ca80c6d7072ed34c8; < 1e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62 (affected, git); ≥ 02d5a2a48bb44e7404b794df87e57588b2fd604e; < 6288baf0c8c4dcfbf206773aede9c1f2269cec28 (affected, git); ≥ 7faac1953ed1f658f719cdf7bb7303fa5eef822c; < 46aea90763832cd6e9b0c2e1c00e6a9512156d4b (affected, git); ≥ 7faac1953ed1f658f719cdf7bb7303fa5eef822c; < 2e2baa8fb5aa4d080cbfeb84c51eff797529f413 (affected, git); ≥ 7faac1953ed1f658f719cdf7bb7303fa5eef822c; < 807e4fb5140c73eb5dba1e399a990db5c1f3cdf8 (affected, git); ≥ 7faac1953ed1f658f719cdf7bb7303fa5eef822c; < c65f1b840ab8ce72ba68f1b63bab7960f8fdfa89 (affected, git); ≥ 7faac1953ed1f658f719cdf7bb7303fa5eef822c; < 078b446efc0f5e496c31bccb72b98af979963a83 (affected, git); ≥ 7faac1953ed1f658f719cdf7bb7303fa5eef822c; < c1c8550e70401159184130a1afc6261db01fc0ce (affected, git); cc7c2818c71ebace207df40cc586c8c74e3d1a59 (affected, git); ec0cddcc2454ab08193beb473978f8f8889b7e24 (affected, git); ≥ 5.10.85; < 5.10.253 (affected, semver); ≥ 5.15.8; < 5.15.203 (affected, semver); ≥ 4.19.221; < 4.20 (affected, semver); ≥ 5.4.165; < 5.5 (affected, semver). Source: CNA: Linux
- Linux / Linux: 5.16 (affected); ≥ 0; < 5.16 (unaffected, semver); ≥ 5.10.253; ≤ 5.10.* (unaffected, semver); ≥ 5.15.203; ≤ 5.15.* (unaffected, semver); ≥ 6.1.167; ≤ 6.1.* (unaffected, semver); ≥ 6.6.130; ≤ 6.6.* (unaffected, semver); ≥ 6.12.78; ≤ 6.12.* (unaffected, semver); ≥ 6.18.19; ≤ 6.18.* (unaffected, semver); ≥ 6.19.9; ≤ 6.19.* (unaffected, semver); ≥ 7.0; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.12% as of 2026-11-06; percentile 2.05%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/1e800e26d54ccf2ddf2ea6d6cbe021c804d8aa62 (CNA: Linux)

- https://git.kernel.org/stable/c/6288baf0c8c4dcfbf206773aede9c1f2269cec28 (CNA: Linux)

- https://git.kernel.org/stable/c/46aea90763832cd6e9b0c2e1c00e6a9512156d4b (CNA: Linux)

- https://git.kernel.org/stable/c/2e2baa8fb5aa4d080cbfeb84c51eff797529f413 (CNA: Linux)

- https://git.kernel.org/stable/c/807e4fb5140c73eb5dba1e399a990db5c1f3cdf8 (CNA: Linux)

- https://git.kernel.org/stable/c/c65f1b840ab8ce72ba68f1b63bab7960f8fdfa89 (CNA: Linux)

- https://git.kernel.org/stable/c/078b446efc0f5e496c31bccb72b98af979963a83 (CNA: Linux)

- https://git.kernel.org/stable/c/c1c8550e70401159184130a1afc6261db01fc0ce (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-43432; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-43432; retrieved 2026-11-06; source updated Not reported

Revision: a6588a90848d894a0463e114fcd6520a5ff3b727235d74c7de3305081c4b4c98

Canonical: https://y2.dev/cve/CVE-2026-43432

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.