---
title: "CVE-2026-89560: Linux Kernel - Broken Access Control"
description: "Linux kernel contains a permission control vulnerability in Landlock where whiteout creation in OverlayFS was improperly guarded, allowing unprivileged users to create whiteout objects without proper LANDLOCK_ACCESS_FS_MAKE_REG permission, exploit requires userspace access to OverlayFS whiteout creation."
url: https://panop.io/threat-heartbeat/CVE-2026-89560/
---

# CVE-2026-89560 Linux Kernel - Broken Access Control

Linux kernel contains a permission control vulnerability in Landlock where whiteout creation in OverlayFS was improperly guarded, allowing unprivileged users to create whiteout objects without proper LANDLOCK\_ACCESS\_FS\_MAKE\_REG permission, exploit requires userspace access to OverlayFS whiteout creation.

CVSS base score 8.4 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.13% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-89560)

## Details

Type

Broken Access Control

Impact

Privilege Escalation

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H

Published

11 September 2026

Updated

15 October 2026

## Vendor fix

Update to the Linux kernel version containing the Landlock patch that requires LANDLOCK\_ACCESS\_FS\_MAKE\_REG for whiteout creation.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-89560](https://nvd.nist.gov/vuln/detail/CVE-2026-89560)
- [https://git.kernel.org/stable/c/d739e32318479086efb8a6bcf5d37cf341b51f8f](https://git.kernel.org/stable/c/d739e32318479086efb8a6bcf5d37cf341b51f8f)
- [https://git.kernel.org/stable/c/dfb10d989056181168ebc16781a8f39520e33200](https://git.kernel.org/stable/c/dfb10d989056181168ebc16781a8f39520e33200)
- [https://git.kernel.org/stable/c/efb4f24fc2b9bcef1c41ff3392894f1fa8fba2a0](https://git.kernel.org/stable/c/efb4f24fc2b9bcef1c41ff3392894f1fa8fba2a0)
- [https://git.kernel.org/stable/c/39fc16597715125529df8f94e016fb00836ee3c1](https://git.kernel.org/stable/c/39fc16597715125529df8f94e016fb00836ee3c1)
- [https://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075](https://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075)
- [https://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16](https://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16)
- [https://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421](https://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)