{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90187 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90187 is a memory corruption 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-90187 and fix it if it is affected.\n\nWhat it is: CVE-2026-90187 is a memory corruption 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-90187 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-90187/ (Markdown: https://insights.sbomify.com/CVE-2026-90187/index.md)","id":"CVE-2026-90187","markdown":"https://insights.sbomify.com/CVE-2026-90187/index.md","name":"CVE-2026-90187","record":{"aliases":["AZL-102177","BELL-CVE-2026-90187","DEBIAN-CVE-2026-90187","GHSA-45hh-qmfr-m7pj","UBUNTU-CVE-2026-90187"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A memory leak in the Linux kernel null_blk driver allows local attackers to exhaust system memory by repeatedly toggling zoned device power states.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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: free zones array on device power-off\n\nnull_init_zoned_dev() allocates dev-\u003ezones when a zoned device is powered\non, but null_del_dev() never frees it on power-off; dev-\u003ezones is only\nfreed later in null_free_dev(), when the configfs directory is removed. If\nthe device is powered off and then on again, null_init_zoned_dev()\nallocates a new array and overwrites the dev-\u003ezones pointer, leaking the\nprevious allocation each power cycle.\n\nFree dev-\u003ezones in null_del_dev() via null_free_zoned_dev() to solve it.\nAnd calling null_free_zoned_dev() in null_free_dev() is no longer necessary\nbecause every caller already invokes null_del_dev() first: via\nnullb_group_drop_item() before nullb_device_release(), in the\nnull_add_dev() error path of null_create_dev(), and in null_destroy_dev().\nRemove the redundant call.\n\nAnd take \u0026lock around zone_cond_store() in the two store wrappers to\nserialize dev-\u003ezones check-and-deref against its alloc/free, which already\nrun under \u0026lock. The reason there was no problem before is that only\nnullb_device_release() or null_exit() frees the dev-\u003ezones, which\nguarantees that subsequent users won't access the configfs interface.","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: free zones array on device power-off","id":"CVE-2026-90187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"null_blk: free global tag_set on init error path","id":"CVE-2026-90188"},"packages":[],"prev":{"headline":"null_blk: reject per-device queue resize for shared tag set","id":"CVE-2026-90186"},"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-21","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel null_blk driver allows local attackers to exhaust system memory by repeatedly toggling zoned device power states.","url":"https://insights.sbomify.com/CVE-2026-90187/"}