{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90275 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90275 is a denial of service 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-90275 and fix it if it is affected.\n\nWhat it is: CVE-2026-90275 is a denial of service 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-90275 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-90275/ (Markdown: https://insights.sbomify.com/CVE-2026-90275/index.md)","id":"CVE-2026-90275","markdown":"https://insights.sbomify.com/CVE-2026-90275/index.md","name":"CVE-2026-90275","record":{"aliases":["AZL-102684","BELL-CVE-2026-90275","DEBIAN-CVE-2026-90275","GHSA-c82r-j325-qwcg","UBUNTU-CVE-2026-90275"],"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":"high_privilege","summary":"A local attacker with high privileges can cause a permanent denial of service in Linux RAID1 arrays by triggering a takeover operation that leaves the array frozen.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nmd/raid1: don't set array_frozen in raid1_takeover()\n\nraid1_takeover() sets conf-\u003earray_frozen = 1 on the newly-allocated\nr1conf and nothing ever clears it, so every I/O to the array stalls\npermanently once _wait_barrier() sees it stuck at 1.\n\nThis used to be harmless: level_store() called mddev_resume() right\nafter pers-\u003erun(), which called raid1_quiesce(mddev, 0) and cleared\narray_frozen back to 0 regardless of what raid1_takeover() set. Commit\nb39f35ebe86d (\"md: don't quiesce in mddev_suspend()\") removed that\nquiesce(mddev, 0) call, so the pre-set now sticks.\n\nsetup_conf() already zero-initializes the new r1conf via kzalloc, so\njust don't set array_frozen here.\n\nSame class of bug as commit 892da88d1cd9 (\"md/raid10: fix a\n'conf-\u003ebarrier' leakage in raid10_takeover()\"), also triggered by\nb39f35ebe86d.","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":"md/raid1: don't set array_frozen in raid1_takeover()","id":"CVE-2026-90275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"md/md-llbitmap: stop daemon timer rearm on destroy","id":"CVE-2026-90276"},"packages":[],"prev":{"headline":"coresight: etm4x: fix underflow for usage of (nrseqstate - 1)","id":"CVE-2026-90274"},"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 local attacker with high privileges can cause a permanent denial of service in Linux RAID1 arrays by triggering a takeover operation that leaves the array frozen.","url":"https://insights.sbomify.com/CVE-2026-90275/"}