PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-90228 Linux CVE debrief

A NULL pointer dereference vulnerability in the Linux kernel's nvmet_execute_identify_ns_zns() function can be triggered when a host issues an Identify command with CNS 05h and CSI 02h targeting a file-backed namespace. This vulnerability has been resolved. The vulnerability arises from a NULL pointer dereference when a file-backed namespace has no block device. Linux kernel administrators and developers should verify their configurations and update to patched versions to mitigate potential impacts.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-17
Original CVE updated
2026-09-18
Advisory published
2026-09-17
Advisory updated
2026-09-18

Who should care

Linux kernel administrators and developers who manage or use Linux kernel-based systems should be aware of this vulnerability and take necessary actions to mitigate potential impacts. They should verify their configurations, update to patched versions, and monitor for Identify commands with CNS 05h and CSI 02h.

Why it matters

A NULL pointer dereference vulnerability in the Linux kernel's nvmet_execute_identify_ns_zns() function can be triggered when a host issues an Identify command with CNS 05h and CSI 02h targeting a file-backed namespace. This vulnerability has been resolved, and Linux kernel administrators and developers should verify their configurations and update to patched versions.

  • Verify Linux kernel configurations for CONFIG_BLK_DEV_ZONED
  • Update to patched Linux kernel versions
  • Monitor for Identify commands with CNS 05h and CSI 02h
  • Assess exposure of file-backed namespaces

Technical summary

The Linux kernel's nvmet_execute_identify_ns_zns() function has a NULL pointer dereference vulnerability when a host issues an Identify command with CNS 05h and CSI 02h targeting a file-backed namespace. The vulnerability is caused by a NULL pointer dereference when a file-backed namespace has no block device. This issue can be resolved by rejecting the command with Invalid Field when the namespace is not backed by a block device. Linux kernel administrators and developers should verify their configurations and update to patched versions.

Defensive priority

Verify Linux kernel configurations and update to patched versions.

Recommended defensive actions

  • Verify Linux kernel configurations for CONFIG_BLK_DEV_ZONED
  • Update to patched Linux kernel versions
  • Monitor for Identify commands with CNS 05h and CSI 02h
  • Assess exposure of file-backed namespaces
  • Review compensating controls for exposed systems
  • Check relevant monitoring, detection, and logs for exposed assets
  • Track exceptions and retest remediated assets

Evidence notes

The vulnerability is caused by a NULL pointer dereference in nvmet_execute_identify_ns_zns() when a file-backed namespace has no block device. The I/O command set is selected by the host-supplied CSI field, exposing any file-backed namespace when CONFIG_BLK_DEV_ZONED is enabled. The official CVE Program record and NIST NVD detail page provide additional context.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-90228 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-90228

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-90228 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90228

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0b4cf43f9ca7118590a338de900edbd6047cd89f

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/1ce8faf90eb0bf5599b90db38500aefea9426485

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/1fb1236312ee1a600de6b3ca560f0b3fd5a50471

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b873099944dae5702b4b6db6814d1f1e8d4cfb00

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/cc29f7082b7ab5e0337f27d1fef16359f05fcffa

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/f594863967d87b7fcbff6e724d51135fd701a13d

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/ff28a93a895912010a7827a0e1445ebe8be53b4d

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.