{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90188 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90188 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-90188 and fix it if it is affected.\n\nWhat it is: CVE-2026-90188 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-90188 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-90188/ (Markdown: https://insights.sbomify.com/CVE-2026-90188/index.md)","id":"CVE-2026-90188","markdown":"https://insights.sbomify.com/CVE-2026-90188/index.md","name":"CVE-2026-90188","record":{"aliases":["AZL-102242","BELL-CVE-2026-90188","DEBIAN-CVE-2026-90188","GHSA-jmg2-qcvp-f7gg","UBUNTU-CVE-2026-90188"],"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 occurs when device creation fails with shared tags enabled, potentially leading to resource exhaustion.","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 global tag_set on init error path\n\nIf shared_tags is enabled, null_setup_tagset() allocates the global tag_set\nvia null_init_global_tag_set(). If device creation later fails, err_dev\ndestroys the default devices and calls unregister_blkdev(), but never frees\nthe global tag_set. Since module init failed, null_exit() is never invoked,\nso the global tag_set's tags and maps are permanently leaked.\n\nFree the global tag_set in err_dev, matching null_exit() which does\nif (tag_set.ops) blk_mq_free_tag_set(\u0026tag_set).","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 global tag_set on init error path","id":"CVE-2026-90188","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"null_blk: register configfs subsystem after creating default devices","id":"CVE-2026-90189"},"packages":[],"prev":{"headline":"null_blk: free zones array on device power-off","id":"CVE-2026-90187"},"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 memory leak in the Linux kernel null_blk driver occurs when device creation fails with shared tags enabled, potentially leading to resource exhaustion.","url":"https://insights.sbomify.com/CVE-2026-90188/"}