{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90185 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90185 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90185 and fix it if it is affected.\n\nWhat it is: CVE-2026-90185 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90185 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90185/ (Markdown: https://insights.sbomify.com/CVE-2026-90185/index.md)","id":"CVE-2026-90185","markdown":"https://insights.sbomify.com/CVE-2026-90185/index.md","name":"CVE-2026-90185","record":{"aliases":["AZL-102582","BELL-CVE-2026-90185","DEBIAN-CVE-2026-90185","GHSA-66h5-crgq-784h","UBUNTU-CVE-2026-90185"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A race condition in the Linux kernel null_blk driver allows local attackers to cause out-of-bounds memory access and system crashes via concurrent configfs writes.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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-\u003eNAME 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-\u003eNAME\nafterwards. This leaves dev-\u003esubmit_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-\u003ezones[] 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"null_blk: serialize configfs attribute stores with the lock","id":"CVE-2026-90185","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"null_blk: reject per-device queue resize for shared tag set","id":"CVE-2026-90186"},"packages":[],"prev":{"headline":"null_blk: serialize configfs attribute updates with device setup","id":"CVE-2026-90184"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel null_blk driver allows local attackers to cause out-of-bounds memory access and system crashes via concurrent configfs writes.","url":"https://insights.sbomify.com/CVE-2026-90185/"}