{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  mm/migrate_device: clear stale mapping after freeing swapcache  __migrate_device_pages() reads the folio mapping before calling folio_free_swap().  When folio_free_swap() succeeds, the folio is removed from the swap cache, but the saved mapping still points to swap_space.  Passing the stale mapping to folio_migrate_mapping() makes it use the mapped-folio path for a folio that is no longer in swapcache.  It can then operate on swap_space.i_pages with invalid reference accounting, eventually triggering a folio reference count BUG.  After a successful split, nr still contains the number of pages in the original large folio, although each resulting page is now a separate order-0 folio.  Reset nr to 1 so each split folio is processed separately, including its own swapcache removal and mapping lookup.  Refresh the saved mapping after folio_free_swap() so the current folio state is used during migration.",
  "id": "DEBIAN-CVE-2026-89755",
  "modified": "2026-09-14T08:47:34.127348970Z",
  "published": "2026-09-11T20:20:06.533Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-89755"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-89755"
  ]
}