{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90190 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90190 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-90190 and fix it if it is affected.\n\nWhat it is: CVE-2026-90190 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-90190 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-90190/ (Markdown: https://insights.sbomify.com/CVE-2026-90190/index.md)","id":"CVE-2026-90190","markdown":"https://insights.sbomify.com/CVE-2026-90190/index.md","name":"CVE-2026-90190","record":{"aliases":["AZL-102345","BELL-CVE-2026-90190","DEBIAN-CVE-2026-90190","GHSA-4pj7-mfrc-7j5j","UBUNTU-CVE-2026-90190"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel null_blk driver allows local attackers to trigger a kernel warning and potential denial of service by racing mkdir operations.","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: use DEFINE_MUTEX for the file-scope mutex\n\nIn null_init(), mutex_init(\u0026lock) currently happens after\nconfigfs_register_subsystem(), which exposes the nullb subsystem to\nuserspace. A racing mkdir() into /sys/kernel/config/nullb/ can reach\nnull_find_dev_by_name() -\u003e mutex_lock(\u0026lock) before the mutex is\ninitialized, trigger warning:\n\n[  123.137788] DEBUG_LOCKS_WARN_ON(lock-\u003emagic != lock)\n[  123.137796] WARNING: kernel/locking/mutex.c:159 at mutex_lock+0x171/0x1c0, CPU#13: mkdir/1301\n[  123.140090] Modules linked in: null_blk(+) nft_fib_inet nft_fib_ipv4\n......\n[  123.154926] Call Trace:\n[  123.155172]  \u003cTASK\u003e\n[  123.155419]  ? __pfx_mutex_lock+0x10/0x10\n[  123.156181]  ? __pfx__raw_spin_lock+0x10/0x10\n[  123.156571]  nullb_group_make_group+0x20/0x100 [null_blk]\n[  123.157011]  configfs_mkdir+0x47b/0xc70\n[  123.157337]  ? __pfx_configfs_mkdir+0x10/0x10\n[  123.157719]  ? may_create_dentry+0x242/0x2e0\n[  123.158061]  vfs_mkdir+0x2a9/0x6c0\n[  123.158352]  filename_mkdirat+0x3dc/0x500\n[  123.158710]  ? __pfx_filename_mkdirat+0x10/0x10\n[  123.159070]  ? strncpy_from_user+0x3a/0x1d0\n[  123.159413]  __x64_sys_mkdir+0x6b/0x90\n[  123.159760]  do_syscall_64+0xea/0x600\n\nReplace the runtime mutex_init(\u0026lock) with a static DEFINE_MUTEX(lock)\ndeclaration to fix this issue.","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: use DEFINE_MUTEX for the file-scope mutex","id":"CVE-2026-90190","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":"mailbox: riscv-sbi-mpxy: validate RPMI notification lengths","id":"CVE-2026-90191"},"packages":[],"prev":{"headline":"null_blk: register configfs subsystem after creating default devices","id":"CVE-2026-90189"},"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 trigger a kernel warning and potential denial of service by racing mkdir operations.","url":"https://insights.sbomify.com/CVE-2026-90190/"}