{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-90185",
  "modified": "2026-10-07T17:22:01Z",
  "upstream": [
    "CVE-2026-90185"
  ],
  "published": "2026-09-17T16:10:40Z",
  "summary": "null_blk: serialize configfs attribute stores with the lock",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: serialize configfs attribute stores with the lock\n\nThe NULLB_DEVICE_ATTR _store takes no lock: apply_fn attributes\n(submit_queues, poll_queues) get dev->NAME written again after apply_fn\nreturns, outside its lock; APPLY=NULL attributes are entirely lockless.\nconfigfs only serializes stores per-open-file, so concurrent stores on\nseparate fds race.\n\nFor apply_fn attributes, once one store's apply_fn has reconfigured the\nhardware, a second (losing) store can still overwrite dev->NAME\nafterwards. This leaves dev->submit_queues out of sync with the live\nqueue count, which is later caught by the WARN_ON_ONCE() in\nnull_map_queues().\n\nFor !apply_fn attributes, power_store()'s null_add_dev() validates and\nbuilds the device under \"lock\" but only sets CONFIGURED afterwards. A store\nslipping in during this window can change a field mid-setup -- for example,\nzone_nr_conv can be pushed above nr_zones after it has already been\nclamped, leading to an out-of-bounds dev->zones[] access.\n\nTake \"lock\" in the macro around the apply_fn call, the CONFIGURED test and\nthe field write, and move it out of nullb_apply_submit_queues()/\nnullb_apply_poll_queues() so both paths are covered once. This serializes\nstores with power_store's setup and with each other.",
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.188",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-90185"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8e839ed5210399a0330a8a6c5885c1d40a537c6d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/88d806d0e1d36246208386a8e55b511c1b3d647c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3945ce8cbce4e328e6fdf0b522dc71e340de19db"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/65cae82fd3c39b53430672cb9e3ecd267471a6ce"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c70994c2862b05e44728912b2ea9487d31e2aea7"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7e7fff51808237703a3a1df6dd5cae1dfd1db86d"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-09-17T16:10:40Z"
  }
}