Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52771: cxl/port: Fix delete_endpoint() vs parent unregistration race

Noroxi assessment

Priority: Monitor (action score 18/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.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 37179fcc916bce8c3cc7b36d67ef814cce55142b, 6b2e428e673b3f55965674a426c40922e91388aa, 8d2ad999ca3c64cb08cf6a58d227b9d9e746d708.

Low priority for now. Upgrade to Linux Linux 37179fcc916bce8c3cc7b36d67ef814cce55142b, 6b2e428e673b3f55965674a426c40922e91388aa, 8d2ad999ca3c64cb08cf6a58d227b9d9e746d708 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/port: Fix delete_endpoint() vs parent unregistration race The CXL subsystem, at cxl_mem ->probe() time, establishes a lineage of ports (struct cxl_port objects) between an endpoint and the root of a CXL topology. Each port including the endpoint port is attached to the cxl_port driver. Given that setup, it follows that when either any port in that lineage goes through a cxl_port ->remove() event, or the memdev goes through a cxl_mem ->remove() event. The hierarchy below the removed port, or the entire hierarchy if the memdev is removed needs to come down. The delete_endpoint() callback is careful to check whether it is being called to tear down the hierarchy, or if it is only being called to teardown the memdev because an ancestor port is going through ->remove(). That care needs to take the device_lock() of the endpoint's parent. Which requires 2 bugs to be fixed: 1/ A reference on the parent is needed to prevent use-after-free scenarios like this signature: BUG: spinlock bad magic on CPU#0, kworker/u56:0/11 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20230524-3.fc38 05/24/2023 Workqueue: cxl_port detach_memdev [cxl_core] RIP: 0010:spin_bug+0x65/0xa0 Call Trace: do_raw_spin_lock+0x69/0xa0 __mutex_lock+0x695/0xb80 delete_endpoint+0xad/0x150 [cxl_core] devres_release_all+0xb8/0x110 device_unbind_cleanup+0xe/0x70 device_release_driver_internal+0x1d2/0x210 detach_memdev+0x15/0x20 [cxl_core] process_one_work+0x1e3/0x4c0 worker_thread+0x1dd/0x3d0 2/ In the case of RCH topologies, the parent device that needs to be locked is not always @port->dev as returned by cxl_mem_find_port(), use endpoint->dev.parent instead.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
May 21, 2024
Updated
Oct 30, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.7
CNA · Linux
4.4
0.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-52771

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

  • linux linux kernel5.18 and later · before 6.5.13
  • linux linux kernel6.6 and later · before 6.6.3

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

    • 5.18affected
    • 8dd2bc0f8e02d39bd80851ca787bcbdb7d495e69 and later · before de0c4ff2fcaec149254b32f18b3ec806b312be74affected · git
    • 8dd2bc0f8e02d39bd80851ca787bcbdb7d495e69 and later · before 37179fcc916bce8c3cc7b36d67ef814cce55142baffected · git
    • 8dd2bc0f8e02d39bd80851ca787bcbdb7d495e69 and later · before 6b2e428e673b3f55965674a426c40922e91388aaaffected · git
    • 8dd2bc0f8e02d39bd80851ca787bcbdb7d495e69 and later · before 8d2ad999ca3c64cb08cf6a58d227b9d9e746d708affected · git
    • before 5.18not affected · semver
    • 6.1.191 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

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.33.1.el9_47.3.0-427.33.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.33.1.el9_45.14.0-427.33.1.el9_4

+96

Same product

linux: all records

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-52761May 21, 2024 · riscv: VMAP_STACK overflow detection thread-safe
    22Monitor
  • ← EarlierCVE-2023-52770May 21, 2024 · f2fs: split initial and dynamic conditions for extent_cache
    22Monitor
  • Later →CVE-2021-47433May 22, 2024 · btrfs: fix abort logic in btrfs_replace_file_extents
    22Monitor

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 Linux37179fcc916bce8c3cc7b36d67ef814cce55142bVendor (CNA)
Linux Linux6b2e428e673b3f55965674a426c40922e91388aaVendor (CNA)
Linux Linux8d2ad999ca3c64cb08cf6a58d227b9d9e746d708Vendor (CNA)
Linux Linuxde0c4ff2fcaec149254b32f18b3ec806b312be74Vendor (CNA)
almalinux:bpftool7.3.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.5.13-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-284.79.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

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

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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.
  • Special conditions such as timing or configuration are required.

If successful

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

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records