CVE-2026-93152: nvme-apple: Use acquire/release for queue enabled state
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 0e9d9fe12da779516dc3899dc9141304675f5416, 840ab22ffa4d859ca40a31e96fc3554688e7a035, 86782a72c6d8c7541813b9ddb009668468601f18.
Low priority for now. Upgrade to Linux Linux 0e9d9fe12da779516dc3899dc9141304675f5416, 840ab22ffa4d859ca40a31e96fc3554688e7a035, 86782a72c6d8c7541813b9ddb009668468601f18 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: 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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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.19affected
- 5bd2927aceba181b84286e00aa2f56e117e699c3 and later · before cbe53ecd696e354bfda8173364f7595759bc562daffected · git
- 5bd2927aceba181b84286e00aa2f56e117e699c3 and later · before 86782a72c6d8c7541813b9ddb009668468601f18affected · git
- 5bd2927aceba181b84286e00aa2f56e117e699c3 and later · before 0e9d9fe12da779516dc3899dc9141304675f5416affected · git
- 5bd2927aceba181b84286e00aa2f56e117e699c3 and later · before e5a79244a3c526a76d930f2ef30aff64528b0c6aaffected · git
- 5bd2927aceba181b84286e00aa2f56e117e699c3 and later · before 840ab22ffa4d859ca40a31e96fc3554688e7a035affected · git
- 5bd2927aceba181b84286e00aa2f56e117e699c3 and later · before f61c934aa084b7440fec681be3f4b481eb5a8609affected · git
- before 5.19not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93150Sep 17, 2026 · cgroup/cpuset: Make nr_deadline_tasks an atomic_t0Monitor
- ← EarlierCVE-2026-93151Sep 17, 2026 · nvmet-rdma: fix response resource leak on queue teardown30Monitor
- Later →CVE-2026-93153Sep 17, 2026 · RDMA/bng_re: return a timeout when firmware responses stall0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0e9d9fe12da779516dc3899dc9141304675f5416 | Vendor (CNA) |
| Linux Linux | 840ab22ffa4d859ca40a31e96fc3554688e7a035 | Vendor (CNA) |
| Linux Linux | 86782a72c6d8c7541813b9ddb009668468601f18 | Vendor (CNA) |
| Linux Linux | cbe53ecd696e354bfda8173364f7595759bc562d | Vendor (CNA) |
| Linux Linux | e5a79244a3c526a76d930f2ef30aff64528b0c6a | Vendor (CNA) |
| Linux Linux | f61c934aa084b7440fec681be3f4b481eb5a8609 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/840ab22ffa4d859ca40a31e96fc3554688e7a035
- git.kernel.org/stable/c/86782a72c6d8c7541813b9ddb009668468601f18
- git.kernel.org/stable/c/cbe53ecd696e354bfda8173364f7595759bc562d
- git.kernel.org/stable/c/e5a79244a3c526a76d930f2ef30aff64528b0c6a
- git.kernel.org/stable/c/f61c934aa084b7440fec681be3f4b481eb5a8609
Vendor advisories and official records. Exploit/PoC links are deliberately left out.