{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.11-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  namespace: reset the old parent's -\u003eovermount in mnt_change_mountpoint()  __umount_mnt() resets -\u003eovermount of the parent when it unmounts the mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the mount to its new parent and leaves the old one pointing at it.  For a mount that is moved beneath in attach_recursive_mnt() that doesn't matter. The new mount has already reset -\u003eovermount of the old parent by the time the old top mount is moved onto it.  It matters for reparent() though. propagate_umount() moves a surviving overmount onto the first ancestor that isn't going to be unmounted. The mount it was taken from is unmounted immediately afterwards. If a file descriptor keeps that unmounted mount alive -\u003eovermount points at the moved mount. That's a dangling pointer and UAF as the moved mount is unmounted and freed.  do_lock_mount() follows -\u003eovermount from the target path under mount_lock. With a file descriptor on such a mount as the target of a mount beneath topmost_overmount() walks into the freed mount and do_lock_mount() takes references on whatever it finds there.  So reset -\u003eovermount of the old parent in mnt_change_mountpoint() the same way __umount_mnt() does. A mount's -\u003eovermount is then always a mount that is attached to it.",
  "id": "DEBIAN-CVE-2026-98995",
  "modified": "2026-10-25T09:47:35.918159013Z",
  "published": "2026-10-23T13:17:21.660Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-98995"
    }
  ],
  "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-98995"
  ]
}