{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.180-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "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: shrinker: fix NULL pointer dereference in debugfs  shrinker_debugfs_add() creates both \"count\" and \"scan\" debugfs files unconditionally.  That assumes every shrinker implements both count_objects() and scan_objects(), which is not guaranteed.  For example, the xen-backend shrinker sets count_objects() but leaves scan_objects() NULL, so writing to its scan file calls through a NULL function pointer and panics the kernel:  BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. Call Trace:  \u003cTASK\u003e  shrinker_debugfs_scan_write+0x12e/0x270  full_proxy_write+0x5f/0x90  vfs_write+0xde/0x420  ? filp_flush+0x75/0x90  ? filp_close+0x1d/0x30  ? do_dup2+0xb8/0x120  ksys_write+0x68/0xf0  ? filp_flush+0x75/0x90  do_syscall_64+0xb3/0x5b0  entry_SYSCALL_64_after_hwframe+0x76/0x7e  The count path has the same issue in principle if a shrinker omits count_objects().  To fix it, only create \"count\" and \"scan\" debugfs files when the corresponding callbacks are present.",
  "id": "DEBIAN-CVE-2026-64417",
  "modified": "2026-09-14T16:47:39.515409394Z",
  "published": "2026-07-25T10:17:25.567Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64417"
    }
  ],
  "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-64417"
  ]
}