# CVE-2026-74273: cxl/region: Block region delete during region creation

> A race condition in the Linux kernel CXL region driver allows local users to trigger a denial of service by deleting regions during creation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-110426, BELL-CVE-2026-74273, DEBIAN-CVE-2026-74273, GHSA-447m-c2m6-7v5x, UBUNTU-CVE-2026-74273

## What is CVE-2026-74273?

CVE-2026-74273 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

cxl/region: Block region delete during region creation

Expand the range lock, rename it "regions_lock", to disable region deletion
in the critical period between construct_region() and attach_target(), as
well as the period between device_add() and registering the remove actions.

Otherwise, userspace can confuse the kernel. It can violate the assumption
the region stays registered through the completion of cxl_add_to_region().
It can violate the assumption that devm_add_action_or_reset() is working
with a live 'struct cxl_region'.

It is ok for the region to disappear outside of those windows as that
mirrors device hotplug flows where the proper locks are held.

## Which versions are affected by CVE-2026-74273?


## How do I fix CVE-2026-74273?

Apply the vendor's patch.

## Is CVE-2026-74273 being exploited?

There is no known exploitation of CVE-2026-74273 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74273 and fix it if it is affected.

What it is: CVE-2026-74273 is a vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74273 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74273/ (Markdown: https://insights.sbomify.com/CVE-2026-74273/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74273
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74273
- OSV: https://osv.dev/vulnerability/CVE-2026-74273

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74273/
Summaries are generated and may contain mistakes; the official description above is the record.