CVE-2024-50226

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-11-09. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

cxl/port: Fix use-after-free, permit out-of-order decoder shutdown

In support of investigating an initialization failure report [1], cxl_test was updated to register mock memory-devices after the mock root-port/bus device had been registered. That led to cxl_test crashing with a use-after-free bug with the following signature:

cxl_port_attach_region: cxl region3: cxl_host_bridge.0:port3 decoder3.0 add: mem0:decoder7.0 @ 0 next: cxl_switch_uport.0 nr_eps: 1 nr_targets: 1 cxl_port_attach_region: cxl region3: cxl_host_bridge.0:port3 decoder3.0 add: mem4:decoder14.0 @ 1 next: cxl_switch_uport.0 nr_eps: 2 nr_targets: 1 cxl_port_setup_targets: cxl region3: cxl_switch_uport.0:port6 target[0] = cxl_switch_dport.0 for mem0:decoder7.0 @ 0 1) cxl_port_setup_targets: cxl region3: cxl_switch_uport.0:port6 target[1] = cxl_switch_dport.4 for mem4:decoder14.0 @ 1 [..] cxld_unregister: cxl decoder14.0: cxl_region_decode_reset: cxl_region region3: mock_decoder_reset: cxl_port port3: decoder3.0 reset 2) mock_decoder_reset: cxl_port port3: decoder3.0: out of order reset, expected decoder3.1 cxl_endpoint_decoder_release: cxl decoder14.0: [..] cxld_unregister: cxl decoder7.0: 3) cxl_region_decode_reset: cxl_region region3: Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6bc3: 0000 [#1] PREEMPT SMP PTI [..] RIP: 0010:to_cxl_port+0x8/0x60 [cxl_core] [..] Call Trace: cxl_region_decode_reset+0x69/0x190 [cxl_core] cxl_region_detach+0xe8/0x210 [cxl_core] cxl_decoder_kill_region+0x27/0x40 [cxl_core] cxld_unregister+0x5d/0x60 [cxl_core]

At 1) a region has been established with 2 endpoint decoders (7.0 and 14.0). Those endpoints share a common switch-decoder in the topology (3.0). At teardown, 2), decoder14.0 is the first to be removed and hits the "out of order reset case" in the switch decoder. The effect though is that region3 cleanup is aborted leaving it in-tact and referencing decoder14.0. At 3) the second attempt to teardown region3 trips over the stale decoder14.0 object which has long since been deleted.

The fix here is to recognize that the CXL specification places no mandate on in-order shutdown of switch-decoders, the driver enforces in-order allocation, and hardware enforces in-order commit. So, rather than fail and leave objects dangling, always remove them.

In support of making cxl_region_decode_reset() always succeed, cxl_region_invalidate_memregion() failures are turned into warnings. Crashing the kernel is ok there since system integrity is at risk if caches cannot be managed around physical address mutation events like CXL region destruction.

A new device_for_each_child_reverse_from() is added to cleanup port->commit_end after all dependent decoders have been disabled. In other words if decoders are allocated 0->1->2 and disabled 1->2->0 then port->commit_end only decrements from 2 after 2 has been disabled, and it decrements all the way to zero since 1 was disabled previously.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 9, 2024

Last Modified

December 11, 2024

Advisory Details (3)

Auto-updated Oct 11, 2026
Patch available.
Web page

cxl/port: Fix use-after-free, permit out-of-order decoder shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e1b52c15c81106456437f8e49575040e489e355
Web page

cxl/port: Fix use-after-free, permit out-of-order decoder shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78c8454fdce0eeee962be004eb6d99860c80dad1
Web page

cxl/port: Fix use-after-free, permit out-of-order decoder shutdown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/101c268bd2f37e965a5468353e62d154db38838e

Vendor Advisories for CVE-2024-50226(1)

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

Patch Availability(14)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.7-1: fixed in 6.11.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.7-1: fixed in 6.11.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 185 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  3. 2026-10-12 17:41 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-10-11 21:07 UTCEG score recompute
  6. 2026-10-11 15:59 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-10 09:25 UTCOSV refresh
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-02 16:15 UTCEG score recompute
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
Show 64 more
  1. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  2. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-09-20 18:44 UTCOSV refresh
  4. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  7. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  8. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  9. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  11. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  12. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  18. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-09-01 18:56 UTCOSV refresh
  22. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  28. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  30. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  32. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  33. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  34. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  35. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  36. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  38. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-08-15 20:07 UTCOSV refresh
  40. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  42. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-07-31 13:12 UTCOSV refresh
  54. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-07-27 14:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-07-23 14:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-07-23 02:42 UTCEG score recompute
  63. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.2% · 14th percentile

Frequently asked(5)

What is CVE-2024-50226?
CVE-2024-50226 is a high-severity vulnerability; its CVE record was published on November 9, 2024. In the Linux kernel, the following vulnerability has been resolved: cxl/port: Fix use-after-free, permit out-of-order decoder shutdown In support of investigating an initialization failure report [1], cxl_test was updated to register mock memory-devices after the mock root-port/bus device had been…
When was the CVE record for CVE-2024-50226 published?
The CVE record for CVE-2024-50226 was published on November 9, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of December 11, 2024; the record at its source may have been updated since.
Is CVE-2024-50226 actively exploited?
CVE-2024-50226 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50226?
CVE-2024-50226 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-50226?
A fix for CVE-2024-50226 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50226 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-50226

Explore →

Is Your Infrastructure Affected by CVE-2024-50226?

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