# CVE-2026-31530: cxl/port: Fix use after free of parent_port in cxl_detach_ep()

Status: published. Published: 2026-04-22. Updated: 2026-11-05.

In the Linux kernel, the following vulnerability has been resolved:

cxl/port: Fix use after free of parent_port in cxl_detach_ep()

cxl_detach_ep() is called during bottom-up removal when all CXL memory
devices beneath a switch port have been removed. For each port in the
hierarchy it locks both the port and its parent, removes the endpoint,
and if the port is now empty, marks it dead and unregisters the port
by calling delete_switch_port(). There are two places during this work
where the parent_port may be used after freeing:

First, a concurrent detach may have already processed a port by the
time a second worker finds it via bus_find_device(). Without pinning
parent_port, it may already be freed when we discover port->dead and
attempt to unlock the parent_port. In a production kernel that's a
silent memory corruption, with lock debug, it looks like this:

[]DEBUG_LOCKS_WARN_ON(__owner_task(owner) != get_current())
[]WARNING: kernel/locking/mutex.c:949 at __mutex_unlock_slowpath+0x1ee/0x310
[]Call Trace:
[]mutex_unlock+0xd/0x20
[]cxl_detach_ep+0x180/0x400 [cxl_core]
[]devm_action_release+0x10/0x20
[]devres_release_all+0xa8/0xe0
[]device_unbind_cleanup+0xd/0xa0
[]really_probe+0x1a6/0x3e0

Second, delete_switch_port() releases three devm actions registered
against parent_port. The last of those is unregister_port() and it
calls device_unregister() on the child port, which can cascade. If
parent_port is now also empty the device core may unregister and free
it too. So by the time delete_switch_port() returns, parent_port may
be free, and the subsequent device_unlock(&parent_port->dev) operates
on freed memory. The kernel log looks same as above, with a different
offset in cxl_detach_ep().

Both of these issues stem from the absence of a lifetime guarantee
between a child port and its parent port.

Establish a lifetime rule for ports: child ports hold a reference to
their parent device until release. Take the reference when the port
is allocated and drop it when released. This ensures the parent is
valid for the full lifetime of the child and eliminates the use after
free window in cxl_detach_ep().

This is easily reproduced with a reload of cxl_acpi in QEMU with CXL
devices present.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 2345df54249c6fb7779e2a72b427ee79ed3eaad5; < b1f62588ab1be6c9535d74348003c86b47ec4abd (affected, git); ≥ 2345df54249c6fb7779e2a72b427ee79ed3eaad5; < d216a4bd138eb57cc4ae7c43b2f709e3482af7e2 (affected, git); ≥ 2345df54249c6fb7779e2a72b427ee79ed3eaad5; < 2c32141462045cf93d54a5146a0ba572b83533dd (affected, git); ≥ 2345df54249c6fb7779e2a72b427ee79ed3eaad5; < f7dc6f381a1e5f068333f1faa9265d6af1df4235 (affected, git); ≥ 2345df54249c6fb7779e2a72b427ee79ed3eaad5; < 19d2f0b97a131198efc2c4ca3eb7f980bba8c2b4 (affected, git). Source: CNA: Linux
- Linux / Linux: 6.3 (affected); ≥ 0; < 6.3 (unaffected, semver); ≥ 6.6.160; ≤ 6.6.* (unaffected, semver); ≥ 6.12.80; ≤ 6.12.* (unaffected, semver); ≥ 6.18.21; ≤ 6.18.* (unaffected, semver); ≥ 6.19.11; ≤ 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.16% as of 2026-11-05; percentile 5.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/b1f62588ab1be6c9535d74348003c86b47ec4abd (CNA: Linux)

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

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

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

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

## Provenance

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

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

Revision: 9b1a73fc165ce7ef8ff8a4c2659d226a7f9e2a41e779565f0d29c084f4bd0df9

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

## 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.