{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.96-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.4-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux-6.12"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.100-1~deb12u1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  mm/swap: add cond_resched() in swap_reclaim_full_clusters to prevent softlockup  We hit a real softlockup in an internal stress test environment.  The workload was LTP memory/swap stress on a large arm64 machine, with 320 CPUs, about 1TB memory and an 8.6GB swap device.  The system was under heavy load and the swap device had a large number of full clusters.  The softlockup was triggered during a stress test after about 3 days.  So, add periodic cond_resched() calls during large full_clusters reclaim operations to prevent softlockup issues.  Detailed call trace as follow:  PID: 3817773  TASK: ffff0883bb28b780  CPU: 48   COMMAND: \"kworker/48:7\"    #0 [ffff800080183d10] __crash_kexec at ffffa4c1361e5de4    #1 [ffff800080183d90] panic at ffffa4c1360d5e9c    #2 [ffff800080183e20] watchdog_timer_fn at ffffa4c136231fa8    ...   #16 [ffff8000c4ad3cb0] swap_cache_del_folio at ffffa4c1363e1614   #17 [ffff8000c4ad3ce0] __try_to_reclaim_swap at ffffa4c1363e4bfc   #18 [ffff8000c4ad3d40] swap_reclaim_full_clusters at ffffa4c1363e5474   #19 [ffff8000c4ad3da0] swap_reclaim_work at ffffa4c1363e550c   #20 [ffff8000c4ad3dc0] process_one_work at ffffa4c136102edc   #21 [ffff8000c4ad3e10] worker_thread at ffffa4c136103398   #22 [ffff8000c4ad3e70] kthread at ffffa4c13610d95c",
  "id": "DEBIAN-CVE-2026-64415",
  "modified": "2026-09-14T16:47:30.802289128Z",
  "published": "2026-07-25T10:17:25.343Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64415"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-64415"
  ]
}