CVE-2026-89759
Last modified
CVE-2026-89759 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup when scanning task stacks Patch series "mm/kmemleak: avoid soft lockup when scanning task", v3. kmemleak_scan() scans every task stack under one rcu_read_lock() with no reschedule point, which can trip the soft lockup watchdog on hosts with very many threads. That prints the following message, depending on the workload+host configuration: watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537] scan_block kmemleak_scan kmemleak_scan_thread kthread Patch 1 walks the tasks with find_ge_pid() so the scan reschedules between tasks Patches 2-3 let the scan loops stop early once a scan is interrupted. This patch (of 3): kmemleak_scan() walks every thread and scans its kernel stack under a single rcu_read_lock() with no reschedule point. On a host with very many threads -- amplified by KASAN/lockdep in debug builds -- this loop can hog a CPU long enough to trip the soft lockup watchdog: watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537] scan_block kmemleak_scan kmemleak_scan_thread kthread A cond_resched() cannot be added directly: the loop runs inside an RCU read-side critical section. Walk the tasks one PID at a time with find_ge_pid(), taking the RCU read lock only to look up and pin each task.
Description
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup when scanning task stacks Patch series "mm/kmemleak: avoid soft lockup when scanning task", v3. kmemleak_scan() scans every task stack under one rcu_read_lock() with no reschedule point, which can trip the soft lockup watchdog on hosts with very many threads. That prints the following message, depending on the workload+host configuration: watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537] scan_block kmemleak_scan kmemleak_scan_thread kthread Patch 1 walks the tasks with find_ge_pid() so the scan reschedules between tasks Patches 2-3 let the scan loops stop early once a scan is interrupted. This patch (of 3): kmemleak_scan() walks every thread and scans its kernel stack under a single rcu_read_lock() with no reschedule point. On a host with very many threads -- amplified by KASAN/lockdep in debug builds -- this loop can hog a CPU long enough to trip the soft lockup watchdog: watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537] scan_block kmemleak_scan kmemleak_scan_thread kthread A cond_resched() cannot be added directly: the loop runs inside an RCU read-side critical section. Walk the tasks one PID at a time with find_ge_pid(), taking the RCU read lock only to look up and pin each task. The stack is then scanned with no lock held, so cond_resched() runs between tasks and the scan stops early on scan_should_stop(). This follows the next_tgid()/task_seq_get_next() iteration pattern and keeps each RCU critical section short.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= c4b28963fd79457315783b3b0f21c01eb88cfdc1, < 9a1b12c06c192290b8479de48f66f1e75d89c4b7; >= c4b28963fd79457315783b3b0f21c01eb88cfdc1, < 3fc8044251de21555fb02c365fa681bab8b0db55; >= c4b28963fd79457315783b3b0f21c01eb88cfdc1, < 1838c704bcb4fd3556cf67513c6f97a39099e35c; >= c4b28963fd79457315783b3b0f21c01eb88cfdc1, < 5d10d4e19e6daa487f0cd0ea6cba472325de92f9 |
| Linux | Linux | 5.10 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89759?
How severe is CVE-2026-89759?
How do I fix CVE-2026-89759?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89753In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89754In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89755In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89756In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89757In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89758In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-8976The RSS Aggregator by Feedzy – Feed to Post, Autoblogging, N…4.3
- CVE-2026-89760In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89761In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89762In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89763In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89764In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-89759?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
