{
  "id": "CVE-2026-89560",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-89560",
  "published_at": "2026-09-11T19:44:32.085Z",
  "title": "landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 8.4,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nlandlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation\n\nWhiteout objects are used in the upper layer of an OverlayFS to\nindicate that the file with this name does not exist in the unified\nview, even if it is present in one of the lower layer file systems.\n\nFor the userspace implementations of OverlayFS (fuse-overlayfs),\nwhiteout objects can be created from userspace as well:\n\n* mknod(2) with S_IFCHR and makedev(0, 0)\n* renameat2(2) with RENAME_WHITEOUT,\n  creating the whiteout in the old place of the moved file.\n\nThis commit guards whiteout creation in both of these cases with\nLANDLOCK_ACCESS_FS_MAKE_REG.  Whiteout objects are *not* considered\ncharacter devices and are not bound to a driver.\n\nLANDLOCK_ACCESS_FS_MAKE_REG describes the same permission class as a\nwhiteout object: creating one is the only S_IFCHR creation that the VFS\nexempts from CAP_MKNOD, so it is as unprivileged as creating a regular\nfile, while LANDLOCK_ACCESS_FS_MAKE_CHAR and\nLANDLOCK_ACCESS_FS_MAKE_BLOCK keep meaning the creation of devices that\nexpose a kernel interface [1].\n\nFor the mknod(2) case, introduce a Landlock erratum.  The creation of\nwhiteout objects through mknod(2) was previously guarded using\nLANDLOCK_ACCESS_FS_MAKE_CHAR, and it is now guarded using\nLANDLOCK_ACCESS_FS_MAKE_REG.\n\nFor the renameat2(2) case, fix a bug: Before this commit, renameat2(2)\nwith RENAME_WHITEOUT would create a directory entry even when all\nLANDLOCK_ACCESS_FS_MAKE_* rights were denied.\n\nThis does not affect normal renames within layered OverlayFS mounts:\nWhen doing a regular rename() on a mounted fuse-overlayfs, it is the\nfuse-overlayfs daemon that exercises renameat2() with RENAME_WHITEOUT,\nand only the Landlock domain of that daemon is checked there.\n\nDepends-on: 49c9e09d9610 (\"landlock: Fix handling of disconnected directories\")\nDepends-on: fe72ce6710cb (\"landlock: Add errata documentation section\")\n[mic: Record why LANDLOCK_ACCESS_FS_MAKE_REG is the matching right, and\nadd link(2) to the user doc]",
  "cvss_by_source": {
    "cna": 8.4
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= cb2c7d1a1776057c9a1f48ed1250d85e94d4850d, \u003c 39fc16597715125529df8f94e016fb00836ee3c1",
          "\u003e= cb2c7d1a1776057c9a1f48ed1250d85e94d4850d, \u003c d739e32318479086efb8a6bcf5d37cf341b51f8f",
          "\u003e= cb2c7d1a1776057c9a1f48ed1250d85e94d4850d, \u003c dfb10d989056181168ebc16781a8f39520e33200",
          "\u003e= cb2c7d1a1776057c9a1f48ed1250d85e94d4850d, \u003c efb4f24fc2b9bcef1c41ff3392894f1fa8fba2a0",
          "\u003e= cb2c7d1a1776057c9a1f48ed1250d85e94d4850d, \u003c 627ce4902df1d737e99306daae5a87c68b876d16",
          "\u003e= cb2c7d1a1776057c9a1f48ed1250d85e94d4850d, \u003c 0c3204aacbe8c07f9e87e3028f28ec6c166a1075",
          "\u003e= cb2c7d1a1776057c9a1f48ed1250d85e94d4850d, \u003c 672fa082d48b21e1fb62cdb184fee41513e53421"
        ],
        "fixed_in": [
          "39fc16597715125529df8f94e016fb00836ee3c1",
          "d739e32318479086efb8a6bcf5d37cf341b51f8f",
          "dfb10d989056181168ebc16781a8f39520e33200",
          "efb4f24fc2b9bcef1c41ff3392894f1fa8fba2a0",
          "627ce4902df1d737e99306daae5a87c68b876d16",
          "0c3204aacbe8c07f9e87e3028f28ec6c166a1075",
          "672fa082d48b21e1fb62cdb184fee41513e53421"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "5.13"
        ],
        "fixed_in": [
          "0",
          "5.15.222",
          "6.1.188",
          "6.6.157",
          "6.12.110",
          "6.18.50",
          "7.2.4",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 39fc16597715125529df8f94e016fb00836ee3c1 or d739e32318479086efb8a6bcf5d37cf341b51f8f or dfb10d989056181168ebc16781a8f39520e33200 or efb4f24fc2b9bcef1c41ff3392894f1fa8fba2a0 or 627ce4902df1d737e99306daae5a87c68b876d16 or 0c3204aacbe8c07f9e87e3028f28ec6c166a1075 or 672fa082d48b21e1fb62cdb184fee41513e53421 or later.",
      "Upgrade Linux to 0 or 5.15.222 or 6.1.188 or 6.6.157 or 6.12.110 or 6.18.50 or 7.2.4 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
