{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-89560", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-09-11T19:38:34.725Z", "datePublished": "2026-09-11T19:44:32.085Z", "dateUpdated": "2026-09-11T19:44:32.085Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-09-11T19:44:32.085Z"}, "descriptions": [{"lang": "en", "value": "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]"}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["include/uapi/linux/landlock.h", "security/landlock/errata/abi-1.h", "security/landlock/fs.c"], "versions": [{"version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d", "lessThan": "627ce4902df1d737e99306daae5a87c68b876d16", "status": "affected", "versionType": "git"}, {"version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d", "lessThan": "0c3204aacbe8c07f9e87e3028f28ec6c166a1075", "status": "affected", "versionType": "git"}, {"version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d", "lessThan": "672fa082d48b21e1fb62cdb184fee41513e53421", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["include/uapi/linux/landlock.h", "security/landlock/errata/abi-1.h", "security/landlock/fs.c"], "versions": [{"version": "5.13", "status": "affected"}, {"version": "0", "lessThan": "5.13", "status": "unaffected", "versionType": "semver"}, {"version": "6.18.50", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.2.4", "lessThanOrEqual": "7.2.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.3-rc1", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.13", "versionEndExcluding": "6.18.50"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.13", "versionEndExcluding": "7.2.4"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "5.13", "versionEndExcluding": "7.3-rc1"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16"}, {"url": "https://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075"}, {"url": "https://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421"}], "title": "landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["include/uapi/linux/landlock.h", "security/landlock/errata/abi-1.h", "security/landlock/fs.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "627ce4902df1d737e99306daae5a87c68b876d16", "status": "affected", "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d", "versionType": "git"}, {"lessThan": "0c3204aacbe8c07f9e87e3028f28ec6c166a1075", "status": "affected", "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d", "versionType": "git"}, {"lessThan": "672fa082d48b21e1fb62cdb184fee41513e53421", "status": "affected", "version": "cb2c7d1a1776057c9a1f48ed1250d85e94d4850d", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["include/uapi/linux/landlock.h", "security/landlock/errata/abi-1.h", "security/landlock/fs.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "5.13"}, {"lessThan": "5.13", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "6.18.*", "status": "unaffected", "version": "6.18.50", "versionType": "semver"}, {"lessThanOrEqual": "7.2.*", "status": "unaffected", "version": "7.2.4", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.3-rc1", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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]"}], "id": "CVE-2026-89560", "lastModified": "2026-09-11T20:19:39.803", "metrics": {}, "published": "2026-09-11T20:19:39.803", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: Linux kernel (Landlock): Security bypass via improper whiteout creation permissions", "id": "2532094", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2532094"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.3", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H", "status": "draft"}, "cwe": "CWE-1220", "details": ["A flaw was found in the Linux kernel's Landlock security module. This vulnerability allowed for the creation of 'whiteout' objects without proper permission checks. Whiteout objects are special files used in OverlayFS to hide underlying files, and their unauthorized creation could lead to unexpected file system behavior or bypass security restrictions. A local attacker could exploit this by using specific mknod(2) or renameat2(2) system calls."], "name": "CVE-2026-89560", "package_state": [{"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Fix deferred", "package_name": "openshift/ose-rhel-coreos-8", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Fix deferred", "package_name": "openshift/ose-rhel-coreos-9", "product_name": "Red Hat OpenShift Container Platform 4"}], "public_date": "2026-09-11T19:44:32Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-89560\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-89560\nhttps://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075\nhttps://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16\nhttps://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421"], "threat_severity": "Moderate"}

{"created": "2026-09-12T04:30:07.741226+00:00", "updated": "2026-09-12T13:30:14.154775+00:00", "vendors": []}