Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52792: cxl/region: Do not try to cleanup after cxl_region_setup_targets() fails

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0718588c7aaa7a1510b4de972370535b61dddd0d, 07ffcd8ec79cf7383e1e45815f4842fd357991c2, 9090c5537c93cd0811ab7bfbd925b57addfffb60.

Low priority for now. Upgrade to Linux Linux 0718588c7aaa7a1510b4de972370535b61dddd0d, 07ffcd8ec79cf7383e1e45815f4842fd357991c2, 9090c5537c93cd0811ab7bfbd925b57addfffb60 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
May 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-52792

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.0affected
    • 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 and later · before 90db4c1d5ebaf574d3c3065c055977982c378a83affected · git
    • 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 and later · before 9090c5537c93cd0811ab7bfbd925b57addfffb60affected · git
    • 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 and later · before 07ffcd8ec79cf7383e1e45815f4842fd357991c2affected · git
    • 5e42bcbc3fef6e759dfb4d3f4cfb394c382b4249 and later · before 0718588c7aaa7a1510b4de972370535b61dddd0daffected · git
    • before 6.0not affected · semver
    • 6.1.64 and later · up to and including 6.1.*not affected · semver
    • 6.5.13 and later · up to and including 6.5.*not affected · semver
    • 6.6.3 and later · up to and including 6.6.*not affected · semver
    • 6.7 and laternot affected · original_commit_for_fix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.0 and later · before 6.1.64
  • linux linux kernel6.2 and later · before 6.5.13
  • linux linux kernel6.6 and later · before 6.6.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.64-16.1.64-1
Debian:13linuxbefore 6.6.8-16.6.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52790May 21, 2024 · swiotlb: fix out-of-bounds TLB allocations with CONFIG_SWIOTLB_DYNAMIC
    22Monitor
  • ← EarlierCVE-2023-52791May 21, 2024 · i2c: core: Run atomic i2c xfer when !preemptible
    22Monitor
  • Later →CVE-2023-52794May 21, 2024 · thermal: intel: powerclamp: fix mismatch in get function for max_idle
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0718588c7aaa7a1510b4de972370535b61dddd0dVendor (CNA)
Linux Linux07ffcd8ec79cf7383e1e45815f4842fd357991c2Vendor (CNA)
Linux Linux9090c5537c93cd0811ab7bfbd925b57addfffb60Vendor (CNA)
Linux Linux90db4c1d5ebaf574d3c3065c055977982c378a83Vendor (CNA)
debian:linux6.1.64-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-50302182 days apartHID: core: zero-initialize the report bufferKEV
    52Plan
  • CVE-2024-47685153 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
    36Monitor
  • CVE-2021-475533 days apartsched/scs: Reset task stack state in bringup_cpu()
    31Monitor
  • CVE-2024-368989 days apartgpiolib: cdev: fix uninitialised kfifo
    31Monitor
  • CVE-2024-2702220 days apartfork: defer linking file vma until vma is fully initialized
    31Monitor
  • CVE-2024-50143170 days apartudf: fix uninit-value use in udf_get_fileshortad
    31Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records