{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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-\u003ezones when a zoned device is powered on, but null_del_dev() never frees it on power-off; dev-\u003ezones 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-\u003ezones pointer, leaking the previous allocation each power cycle.  Free dev-\u003ezones 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 \u0026lock around zone_cond_store() in the two store wrappers to serialize dev-\u003ezones check-and-deref against its alloc/free, which already run under \u0026lock. The reason there was no problem before is that only nullb_device_release() or null_exit() frees the dev-\u003ezones, which guarantees that subsequent users won't access the configfs interface.",
  "id": "DEBIAN-CVE-2026-90187",
  "modified": "2026-09-18T04:47:31.452955617Z",
  "published": "2026-09-17T17:17:13.270Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-90187"
    }
  ],
  "upstream": [
    "CVE-2026-90187"
  ]
}