# CVE-2026-72131: nvme-apple: Prevent shared tags across queues on Apple A11

> A flaw in the Apple A11 NVMe driver allows firmware crashes via duplicate tags, causing denial of service for local attackers.

- **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:** 15 Aug 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-105957, BELL-CVE-2026-72131, DEBIAN-CVE-2026-72131, GHSA-ccmv-h994-rmq2, UBUNTU-CVE-2026-72131

## What is CVE-2026-72131?

CVE-2026-72131 is a denial of service 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:

nvme-apple: Prevent shared tags across queues on Apple A11

On Apple A11, tags of pending commands must be unique across the admin
and IO queues, else the firmware crashes with
"duplicate tag error for tag N", with N being the tag.

Apply the existing workaround for M1 of reserving two tags for the admin
queue to A11.

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


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

Apply the vendor's patch.

## Is CVE-2026-72131 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72131 is a denial of service 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-72131 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-72131/ (Markdown: https://insights.sbomify.com/CVE-2026-72131/index.md)
```

## Sources

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

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