CVE-2023-52792
cxl/region: Do not try to cleanup after cxl_region_setup_targets() fails
Reported by linux · Published May 21, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | 9090c5537c93cd0811ab7bfbd925b57addfffb60, 07ffcd8ec79cf7383e1e45815f4842fd357991c2, 0718588c7aaa7a1510b4de972370535b61dddd0d |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249, 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249, 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 |
| Linux | Linux | 6.0, 0, 6.1.64 |
| Linux | Linux | 6.5.13, 6.6.3, 6.7 |
| linux | linux_kernel | 6.0, 6.0, 6.0 |
Timeline
- May 21, 2024 CVE Published
- May 22, 2024 EPSS Score (30 in total, the first dated here)
- Oct 5, 2024 Coalition ESS Score (4 in total, the first dated here)
- Jan 25, 2026 Security Advisory (259 in total, the first dated here)
- Oct 30, 2026 Distribution Patch (166 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2023-52792
vulnetix vdb fixes CVE-2023-52792
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2023-52792/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart