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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)
EPSS
2.6%
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

Vendor Advisories for CVE-2026-31530(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 38× 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 136 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 75 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-19 19:25 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-18 17:52 UTCEPSS rescore
  12. 2026-06-17 17:53 UTCEPSS rescore
  13. 2026-06-16 17:52 UTCEPSS rescore
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-15 02:41 UTCEG score recompute
  16. 2026-06-15 02:40 UTCGHSA enrichment
  17. 2026-06-14 23:18 UTCEPSS rescore
  18. 2026-06-14 12:37 UTCEG score recompute
  19. 2026-06-14 12:36 UTCGHSA enrichment
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 01:54 UTCEG score recompute
  24. 2026-06-12 01:54 UTCGHSA enrichment
  25. 2026-06-11 14:43 UTCEG score recompute
  26. 2026-06-11 14:43 UTCGHSA enrichment
  27. 2026-06-11 14:00 UTCEPSS rescore
  28. 2026-06-10 22:18 UTCEPSS rescore
  29. 2026-06-10 13:22 UTCEPSS rescore
  30. 2026-06-10 13:15 UTCEG score recompute
  31. 2026-06-10 13:15 UTCGHSA enrichment
  32. 2026-06-10 02:04 UTCEG score recompute
  33. 2026-06-10 02:04 UTCGHSA enrichment
  34. 2026-06-09 14:53 UTCEG score recompute
  35. 2026-06-09 14:53 UTCGHSA enrichment
  36. 2026-06-09 03:43 UTCEG score recompute
  37. 2026-06-09 03:43 UTCGHSA enrichment
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 05:53 UTCEG score recompute
  41. 2026-06-08 05:53 UTCGHSA enrichment
  42. 2026-06-07 18:43 UTCEG score recompute
  43. 2026-06-07 18:43 UTCGHSA enrichment
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 15:25 UTCEPSS rescore
  46. 2026-06-07 15:25 UTCEPSS rescore
  47. 2026-06-07 07:32 UTCEG score recompute
  48. 2026-06-07 07:32 UTCGHSA enrichment
  49. 2026-06-06 20:21 UTCEG score recompute
  50. 2026-06-06 20:21 UTCGHSA enrichment
  51. 2026-06-06 13:47 UTCEPSS rescore
  52. 2026-06-06 13:47 UTCEPSS rescore
  53. 2026-06-06 05:28 UTCEG score recompute
  54. 2026-06-06 05:28 UTCGHSA enrichment
  55. 2026-06-05 22:47 UTCEPSS rescore
  56. 2026-06-05 22:47 UTCEPSS rescore
  57. 2026-06-05 17:07 UTCEG score recompute
  58. 2026-06-05 17:07 UTCGHSA enrichment
  59. 2026-06-05 06:10 UTCEPSS rescore
  60. 2026-06-05 06:10 UTCEPSS rescore
  61. 2026-06-05 03:23 UTCEG score recompute
  62. 2026-06-05 03:23 UTCGHSA enrichment
  63. 2026-06-04 13:43 UTCEG score recompute
  64. 2026-06-04 13:43 UTCGHSA enrichment
  65. 2026-06-04 13:12 UTCEPSS rescore
  66. 2026-06-04 13:12 UTCEPSS rescore
  67. 2026-06-04 01:09 UTCEG score recompute
  68. 2026-06-04 01:09 UTCGHSA enrichment
  69. 2026-06-03 13:58 UTCEG score recompute
  70. 2026-06-03 13:58 UTCGHSA enrichment
  71. 2026-06-03 02:47 UTCEG score recompute
  72. 2026-06-03 02:47 UTCGHSA enrichment
  73. 2026-06-02 20:13 UTCEPSS rescore
  74. 2026-06-02 20:13 UTCEPSS rescore
  75. 2026-06-02 15:23 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 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.