{
  "cveId": "CVE-2026-89759",
  "url": "https://patchblox.com/security/cve/CVE-2026-89759",
  "summary": "CVE-2026-89759 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-89759, released September 23, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  mm/kmemleak: avoid soft lockup when scanning tas...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  mm/kmemleak: avoid soft lockup when scanning task stacks  Patch series \u0022mm/kmemleak: avoid soft lockup when scanning task\u0022, 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\u002Bhost 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.",
  "published": "2026-09-11T20:20:06Z",
  "severity": "",
  "epss": 0.00198,
  "epssPercentile": 0.09537,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.111-1",
      "fix": "DEBIAN-CVE-2026-89759",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-89759",
      "released": "2026-09-23T19:19:02Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.2.6-1",
      "fix": "DEBIAN-CVE-2026-89759",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-89759",
      "released": "2026-09-23T19:19:02Z"
    },
    {
      "platform": "linux",
      "product": "linux-6.12",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.12.111-1~deb12u1",
      "fix": "DEBIAN-CVE-2026-89759",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-89759",
      "released": "2026-09-23T19:19:02Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T01:18:40Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}