CVE-2023-52792cxl/region: Do not try to cleanup after cxl_region_setup_targets() fails
- 5.5MediumCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: cxl/region: Do not try to cleanup after cxl_region_setup_targets() fails Commit 5e42bcbc3fef ("cxl/region: decrement ->nr_targets on error in cxl_region_attach()") tried to avoid 'eiw' initialization errors when ->nr_targets exceeded 16, by just decrementing ->nr_targets when cxl_region_setup_targets() failed. Commit 86987c766276 ("cxl/region: Cleanup target list on attach error") extended that cleanup to also clear cxled->pos and p->targets[pos]. The initialization error was incidentally fixed separately by: Commit 8d4285425714 ("cxl/region: Fix port setup uninitialized variable warnings") which was merged a few days after 5e42bcbc3fef. But now the original cleanup when cxl_region_setup_targets() fails prevents endpoint and switch decoder resources from being reused: 1) the cleanup does not set the decoder's region to NULL, which results in future dpa_size_store() calls returning -EBUSY 2) the decoder is not properly freed, which results in future commit errors associated with the upstream switch Now that the initialization errors were fixed separately, the proper cleanup for this case is to just return immediately. Then the resources associated with this target get cleanup up as normal when the failed region is deleted. The ->nr_targets decrement in the error case also helped prevent a p->targets[] array overflow, so add a new check to prevent against that overflow. Tested by trying to create an invalid region for a 2 switch * 2 endpoint topology, and then following up with creating a valid region.
Timeline
ID reserved
By Linux
Published
- 24 months later
· 24 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 – < 90db4c1d5ebaf574d3c3065c055977982c378a83
- affected 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 – < 9090c5537c93cd0811ab7bfbd925b57addfffb60
- affected 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 – < 07ffcd8ec79cf7383e1e45815f4842fd357991c2
- affected 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 – < 0718588c7aaa7a1510b4de972370535b61dddd0d
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.64 – ≤ 6.1.*
- unaffected 6.5.13 – ≤ 6.5.*
- unaffected 6.6.3 – ≤ 6.6.*
- unaffected 6.7 – ≤ *
References
References4
- https://git.kernel.org/stable/c/90db4c1d5ebaf574d3c3065c055977982c378a83 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/9090c5537c93cd0811ab7bfbd925b57addfffb60 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/07ffcd8ec79cf7383e1e45815f4842fd357991c2 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/0718588c7aaa7a1510b4de972370535b61dddd0d (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-59509 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-52792)Record last updated .