{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89759 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89759 is a denial of service vulnerability in Linux, published on 11 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-89759 and fix it if it is affected.\n\nWhat it is: CVE-2026-89759 is a denial of service vulnerability in Linux, published on 11 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-89759 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-89759/ (Markdown: https://insights.sbomify.com/CVE-2026-89759/index.md)","id":"CVE-2026-89759","markdown":"https://insights.sbomify.com/CVE-2026-89759/index.md","name":"CVE-2026-89759","record":{"aliases":["AZL-100301","BELL-CVE-2026-89759","DEBIAN-CVE-2026-89759","GHSA-cr6x-j7pj-fq6g","UBUNTU-CVE-2026-89759"],"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":"none","summary":"A local attacker can trigger a soft lockup in the Linux kernel's kmemleak scanner, causing a denial of service on systems with many threads.","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\nmm/kmemleak: avoid soft lockup when scanning task stacks\n\nPatch series \"mm/kmemleak: avoid soft lockup when scanning task\", v3.\n\nkmemleak_scan() scans every task stack under one rcu_read_lock() with no\nreschedule point, which can trip the soft lockup watchdog on hosts with\nvery many threads.\n\nThat prints the following message, depending on the workload+host\nconfiguration:\n\n      watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537]\n       scan_block\n       kmemleak_scan\n       kmemleak_scan_thread\n       kthread\n\nPatch 1 walks the tasks with find_ge_pid() so the scan reschedules between\ntasks\n\nPatches 2-3 let the scan loops stop early once a scan is interrupted.\n\nThis patch (of 3):\n\nkmemleak_scan() walks every thread and scans its kernel stack under a\nsingle rcu_read_lock() with no reschedule point.  On a host with very many\nthreads -- amplified by KASAN/lockdep in debug builds -- this loop can hog\na CPU long enough to trip the soft lockup watchdog:\n\n  watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537]\n   scan_block\n   kmemleak_scan\n   kmemleak_scan_thread\n   kthread\n\nA cond_resched() cannot be added directly: the loop runs inside an RCU\nread-side critical section.\n\nWalk the tasks one PID at a time with find_ge_pid(), taking the RCU read\nlock only to look up and pin each task.  The stack is then scanned with no\nlock held, so cond_resched() runs between tasks and the scan stops early\non scan_should_stop().  This follows the next_tgid()/task_seq_get_next()\niteration pattern and keeps each RCU critical section short.","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/kmemleak: avoid soft lockup when scanning task stacks","id":"CVE-2026-89759","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":"mm, swap: don't free a hibernation slot that is in the swap cache","id":"CVE-2026-89760"},"packages":[],"prev":{"headline":"mm/mempolicy: skip non-present PMDs when queueing folios","id":"CVE-2026-89758"},"products":["Linux"],"published":"2026-09-11","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 local attacker can trigger a soft lockup in the Linux kernel's kmemleak scanner, causing a denial of service on systems with many threads.","url":"https://insights.sbomify.com/CVE-2026-89759/"}