{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89986 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89986 is a high-severity denial of service vulnerability in Linux, published on 16 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-89986 and fix it if it is affected.\n\nWhat it is: CVE-2026-89986 is a high-severity denial of service vulnerability in Linux, published on 16 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-89986 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-89986/ (Markdown: https://insights.sbomify.com/CVE-2026-89986/index.md)","id":"CVE-2026-89986","markdown":"https://insights.sbomify.com/CVE-2026-89986/index.md","name":"CVE-2026-89986","record":{"aliases":["BELL-CVE-2026-89986","DEBIAN-CVE-2026-89986","GHSA-f5rq-g72v-q29m","UBUNTU-CVE-2026-89986"],"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 kernel bug causes a sleeping allocation in atomic context, leading to system crashes or instability when specific memory policies are active.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempolicy: fix sleeping allocation in alloc_pages_bulk_weighted_interleave()\n\nsyzbot reported a sleeping function called from invalid context splat in\nbucket_table_alloc().\n\nWhen rhashtable_insert_slow() rehashes the table under rcu_read_lock(), it\ncalls bucket_table_alloc(..., GFP_ATOMIC | __GFP_NOWARN).  If the bucket\ntable allocation uses vmalloc, __vmalloc_node_range_noprof() invokes\nvm_area_alloc_pages() -\u003e alloc_pages_bulk_mempolicy_noprof() with the\npassed GFP_ATOMIC flags.\n\nIf the current task has an MPOL_WEIGHTED_INTERLEAVE mempolicy,\nalloc_pages_bulk_weighted_interleave() is called and currently hardcodes\nGFP_KERNEL when allocating the temporary weights array, triggering a\nmight_alloc() splat in atomic/RCU contexts.\n\nPass the gfp flags (masked with GFP_RECLAIM_MASK to strip page-allocator\nzone modifiers like __GFP_HIGHMEM) received by\nalloc_pages_bulk_weighted_interleave() to kmalloc() instead of hardcoding\nGFP_KERNEL.  Since the weights buffer is immediately initialized in full,\nkmalloc() is sufficient.","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":"mm/mempolicy: fix sleeping allocation in alloc_pages_bulk_weighted_interleave()","id":"CVE-2026-89986","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"mm/huge_memory: transfer the pmd dirty bit to the folio on zap","id":"CVE-2026-89987"},"packages":[],"prev":{"headline":"memcg: keep folio's objcg same as its node","id":"CVE-2026-89985"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A kernel bug causes a sleeping allocation in atomic context, leading to system crashes or instability when specific memory policies are active.","url":"https://insights.sbomify.com/CVE-2026-89986/"}