nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() (CVE-2026-90227) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90227

nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed()

Answer in brief

CVE-2026-90227 records a Unknown severity vulnerability in nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c35cd98eed1a863e8dd51073953563cd8c907f68 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <95b0591d51dbf9e618d7845883d535e88ad7c8af \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <736b7c6adc7a65c4411beff197b6a634f7a6ca27 \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b116e9dae433ff631f94c36c61a7a78fe400ed1e \|\| >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b53d495c7f0db46b6748b5ade48371a10dd5d3bc \|\| >=0 <6.6.157 \|\| >=0 <6.12.110 \|\| >=0 <6.18.52 \|\| >=0 <7.2.6	c35cd98eed1a863e8dd51073953563cd8c907f68, 95b0591d51dbf9e618d7845883d535e88ad7c8af, 736b7c6adc7a65c4411beff197b6a634f7a6ca27, b116e9dae433ff631f94c36c61a7a78fe400ed1e, b53d495c7f0db46b6748b5ade48371a10dd5d3bc, 6.6.157, 6.12.110, 6.18.52, 7.2.6

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux.
Review the reported fix. Update Linux/Linux to c35cd98eed1a863e8dd51073953563cd8c907f68 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() Unlike IO_CMD / IO64_CMD, NVME_IOCTL_SUBMIT_IO never calls nvme_cmd_allowed(). Unprivileged callers can thus issue I/O on a partition device or write through a read-only file descriptor. Pass flags and open_for_write through and reject disallowed commands with -EACCES.

Quoted source text, attributed separately from HOL analysis.