# CVE-2026-93152: nvme-apple: Use acquire/release for queue enabled state

> A race condition in the Apple NVMe driver's queue initialization can lead to system instability or denial of service due to improper memory ordering.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102222, BELL-CVE-2026-93152, DEBIAN-CVE-2026-93152, GHSA-5wm2-2pgr-vhm6, UBUNTU-CVE-2026-93152

## What is CVE-2026-93152?

CVE-2026-93152 is a vulnerability in Linux, published on 17 Sep 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:

nvme-apple: Use acquire/release for queue enabled state

apple_nvme_init_queue() initializes queue state and then marks the queue
enabled. The interrupt and request paths check enabled before using that
queue state.

The old wmb() after WRITE_ONCE(enabled, true) does not publish the
earlier initialization before enabled becomes visible. Use a release store
when enabling the queue and acquire loads when testing it.

Although the shutdown-side enabled accesses are not used for publishing
queue initialization, use helpers for them as well for consistency.

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


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

Apply the vendor's patch.

## Is CVE-2026-93152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93152 is a vulnerability in Linux, published on 17 Sep 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-93152 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-93152/ (Markdown: https://insights.sbomify.com/CVE-2026-93152/index.md)
```

## Sources

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

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