CVE-2026-31530

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 22, 2026

Last Modified

April 28, 2026

Advisory Details (4)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

cxl/port: Fix use after free of parent_port in cxl_detach_ep() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f7dc6f381a1e5f068333f1faa9265d6af1df4235
generic

cxl/port: Fix use after free of parent_port in cxl_detach_ep() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d216a4bd138eb57cc4ae7c43b2f709e3482af7e2
generic

cxl/port: Fix use after free of parent_port in cxl_detach_ep() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c32141462045cf93d54a5146a0ba572b83533dd
generic

cxl/port: Fix use after free of parent_port in cxl_detach_ep() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19d2f0b97a131198efc2c4ca3eb7f980bba8c2b4

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-687.38.1.el9_82026-08-11redhat
redhatkernel-0:6.12.0-211.37.1.el10_22026-07-21redhat
linuxKernel @ 6.12.80osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 228 total refreshes for this CVE.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-10 09:34 UTCEPSS rescore
  3. 2026-09-08 22:00 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 14:11 UTCEPSS rescore
  9. 2026-09-02 02:38 UTCOSV refresh
  10. 2026-09-01 13:53 UTCEPSS rescore
  11. 2026-09-01 04:39 UTCEPSS rescore
  12. 2026-09-01 04:39 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 14:17 UTCEPSS rescore
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 05:58 UTCEG score recompute
  4. 2026-08-16 05:58 UTCVendor advisory
  5. 2026-08-16 05:58 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 15:29 UTCVendor advisory
  9. 2026-08-14 15:29 UTCGHSA enrichment
  10. 2026-08-14 04:18 UTCEG score recompute
  11. 2026-08-14 04:18 UTCVendor advisory
  12. 2026-08-14 04:18 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 08:39 UTCVendor advisory
  15. 2026-08-13 08:39 UTCGHSA enrichment
  16. 2026-08-12 18:30 UTCEG score recompute
  17. 2026-08-12 18:30 UTCVendor advisory
  18. 2026-08-12 18:30 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 16:45 UTCVendor advisory
  21. 2026-08-11 16:45 UTCGHSA enrichment
  22. 2026-08-11 02:18 UTCEG score recompute
  23. 2026-08-11 02:18 UTCVendor advisory
  24. 2026-08-11 02:18 UTCGHSA enrichment
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 13:05 UTCVendor advisory
  27. 2026-08-10 13:05 UTCGHSA enrichment
  28. 2026-08-10 01:54 UTCVendor advisory
  29. 2026-08-10 01:54 UTCGHSA enrichment
  30. 2026-08-09 14:43 UTCEG score recompute
  31. 2026-08-09 14:43 UTCVendor advisory
  32. 2026-08-09 14:43 UTCGHSA enrichment
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 03:32 UTCEG score recompute
  35. 2026-08-09 03:32 UTCVendor advisory
  36. 2026-08-09 03:32 UTCGHSA enrichment
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-08 11:13 UTCVendor advisory
  39. 2026-08-08 11:13 UTCGHSA enrichment
  40. 2026-08-07 23:57 UTCEG score recompute
  41. 2026-08-07 23:57 UTCVendor advisory
  42. 2026-08-07 23:57 UTCGHSA enrichment
  43. 2026-08-07 12:47 UTCVendor advisory
  44. 2026-08-07 12:47 UTCGHSA enrichment
  45. 2026-08-06 21:32 UTCEG score recompute
  46. 2026-08-06 21:32 UTCVendor advisory
  47. 2026-08-06 21:31 UTCGHSA enrichment
  48. 2026-08-06 13:46 UTCEPSS rescore
  49. 2026-08-06 10:21 UTCVendor advisory
  50. 2026-08-06 10:21 UTCGHSA enrichment
  51. 2026-08-05 23:04 UTCEG score recompute
  52. 2026-08-05 23:04 UTCVendor advisory
  53. 2026-08-05 23:04 UTCGHSA enrichment
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-04 10:38 UTCEPSS rescore
  56. 2026-08-03 21:14 UTCEG score recompute
  57. 2026-08-03 21:14 UTCVendor advisory
  58. 2026-08-03 21:14 UTCGHSA enrichment
  59. 2026-08-03 10:36 UTCEPSS rescore
  60. 2026-08-02 23:18 UTCVendor advisory
  61. 2026-08-02 23:18 UTCGHSA enrichment
  62. 2026-08-02 12:08 UTCEG score recompute
  63. 2026-08-02 12:08 UTCVendor advisory
  64. 2026-08-02 12:07 UTCGHSA enrichment
  65. 2026-08-02 02:27 UTCEPSS rescore
  66. 2026-08-01 04:16 UTCEPSS rescore
  67. 2026-07-30 16:27 UTCEPSS rescore
  68. 2026-07-30 01:30 UTCEPSS rescore
  69. 2026-07-28 15:36 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-25 14:17 UTCEPSS rescore
  74. 2026-07-24 14:17 UTCEPSS rescore
  75. 2026-07-23 03:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-31530?
CVE-2026-31530 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: cxl/port: Fix use after free of parentport in cxldetach_ep() cxldetachep() 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…
When was CVE-2026-31530 disclosed?
CVE-2026-31530 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31530 actively exploited?
CVE-2026-31530 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-31530?
CVE-2026-31530 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31530?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31530, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31530

Explore →

Is Your Infrastructure Affected by CVE-2026-31530?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.