Skip to content
Heist/ feed
Back to feed
UnratedFix available

null_blk: free zones array on device power-off

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: null_blk: free zones array on device power-off null_init_zoned_dev() allocates dev->zones when a zoned device is powered on, but null_del_dev() never frees it on power-off; dev->zones is only freed later in null_free_dev(), when the configfs directory is removed. If the device is powered off and then on again, null_init_zoned_dev() allocates a new array and overwrites the dev->zones pointer, leaking the previous allocation each power cycle. Free dev->zones in null_del_dev() via null_free_zoned_dev() to solve it. And calling null_free_zoned_dev() in null_free_dev() is no longer necessary because every caller already invokes null_del_dev() first: via nullb_group_drop_item() before nullb_device_release(), in the null_add_dev() error path of null_create_dev(), and in null_destroy_dev(). Remove the redundant call. And take &lock around zone_cond_store() in the two store wrappers to serialize dev->zones check-and-deref against its alloc/free, which already run under &lock. The reason there was no problem before is that only nullb_device_release() or null_exit() frees the dev->zones, which guarantees that subsequent users won't access the configfs interface.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.1.191, 6.12.110, 6.18.52, 6.6.160, 7.2.6
CVEs
CVE-2026-90187
Confirmed fixed CVEs
Not specified
Updated in this feed
6 Nov 2026, 00:27 UTC · Revision 1

Source evidence

null_blk: free zones array on device power-off

core-osv · Original source

Published 17 Sept 2026, 16:07 UTC

In the Linux kernel, the following vulnerability has been resolved: null_blk: free zones array on device power-off null_init_zoned_dev() allocates dev->zones when a zoned device is powered on, but null_del_dev() never frees it on power-off; dev->zones is only freed later in null_free_dev(), when the configfs directory is removed. If the device is powered off and then on again, null_init_zoned_dev() allocates a new array and overwrites the dev->zones pointer, leaking the previous allocation each power cycle. Free dev->zones in null_del_dev() via null_free_zoned_dev() to solve it. And calling null_free_zoned_dev() in null_free_dev() is no longer necessary because every caller already invokes null_del_dev() first: via nullb_group_drop_item() before nullb_device_release(), in the null_add_dev() error path of null_create_dev(), and in null_destroy_dev(). Remove the redundant call. And take &lock around zone_cond_store() in the two store wrappers to serialize dev->zones check-and-deref against its alloc/free, which already run under &lock. The reason there was no problem before is that only nullb_device_release() or null_exit() frees the dev->zones, which guarantees that subsequent users won't access the configfs interface.

osv:CVE-2026-90187

Kernel

Fixed versions: 6.1.191, 6.6.160, 6.12.110, 6.18.52, 7.2.6

Complete source record
{
  "id": "5c5feb2960c89edb5cb245c0ce336564f89e73d5815a9a66f82697d7ea94b38e",
  "url": "https://osv.dev/vulnerability/CVE-2026-90187",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "null_blk: free zones array on device power-off",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: null_blk: free zones array on device power-off null_init_zoned_dev() allocates dev->zones when a zoned device is powered on, but null_del_dev() never frees it on power-off; dev->zones is only freed later in null_free_dev(), when the configfs directory is removed. If the device is powered off and then on again, null_init_zoned_dev() allocates a new array and overwrites the dev->zones pointer, leaking the previous allocation each power cycle. Free dev->zones in null_del_dev() via null_free_zoned_dev() to solve it. And calling null_free_zoned_dev() in null_free_dev() is no longer necessary because every caller already invokes null_del_dev() first: via nullb_group_drop_item() before nullb_device_release(), in the null_add_dev() error path of null_create_dev(), and in null_destroy_dev(). Remove the redundant call. And take &lock around zone_cond_store() in the two store wrappers to serialize dev->zones check-and-deref against its alloc/free, which already run under &lock. The reason there was no problem before is that only nullb_device_release() or null_exit() frees the dev->zones, which guarantees that subsequent users won't access the configfs interface.",
    "evidence": "osv:CVE-2026-90187",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.1.191",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.160",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.110",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.52",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.2.6",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-90187",
      "aliases": [
        "CVE-2026-90187"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "ca4b2a011948fae4e4d31490107db4926385a983"
                },
                {
                  "fixed": "26d21585caa61c30d0f3044a1e6d172456148c9f"
                },
                {
                  "fixed": "08a31a2cc3d1cea67ccd292d01511cd0a72d4656"
                },
                {
                  "fixed": "056be41932c95aabdb3c2967d1ef4978f17a0225"
                },
                {
                  "fixed": "b2437d37fcc31fce8a5da1cc1739e284814d2491"
                },
                {
                  "fixed": "0a3afab87124171022fb3579502fa38ef5b311c9"
                },
                {
                  "fixed": "2a6357a9b935a34f5508618fee8a7fffbf7722a8"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90187.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "4.19.0"
                },
                {
                  "fixed": "6.1.191"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.160"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.110"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.52"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.2.6"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90187.json"
          }
        }
      ],
      "modified": "2026-11-01T02:30:52.807795279Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/056be41932c95aabdb3c2967d1ef4978f17a0225",
        "https://git.kernel.org/stable/c/08a31a2cc3d1cea67ccd292d01511cd0a72d4656",
        "https://git.kernel.org/stable/c/0a3afab87124171022fb3579502fa38ef5b311c9",
        "https://git.kernel.org/stable/c/26d21585caa61c30d0f3044a1e6d172456148c9f",
        "https://git.kernel.org/stable/c/2a6357a9b935a34f5508618fee8a7fffbf7722a8",
        "https://git.kernel.org/stable/c/b2437d37fcc31fce8a5da1cc1739e284814d2491",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90187.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-90187",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90187.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-90187",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 513481,
  "published_at": "2026-09-17T16:07:09.683+00:00"
}