PatchSiren cyber security CVE debrief
CVE-2026-89560 Linux CVE debrief
A Linux kernel vulnerability, CVE-2026-89560, has been addressed with a commit requiring LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation in OverlayFS. This change guards whiteout creation via mknod(2) and renameat2(2) with RENAME_WHITEOUT, introducing a Landlock erratum for mknod(2) cases and fixing a bug in renameat2(2) handling. The update impacts Linux kernel administrators, security teams, and developers using OverlayFS, who should assess exposure and verify Landlock configurations.
- Vendor
- Linux
- Product
- Linux kernel
- CVSS
- HIGH 8.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-11
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-09-11
- Advisory updated
- 2026-09-11
Who should care
Linux kernel administrators, security teams, and developers using OverlayFS should assess exposure and verify Landlock configurations to ensure proper access control for whiteout creation. This includes reviewing and updating Landlock configurations, assessing Linux kernel deployments for potential exposure, and verifying system configurations to update to the latest kernel version if necessary.
Why it matters
The Linux kernel vulnerability CVE-2026-89560 requires LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation in OverlayFS, addressing potential security concerns. Linux kernel administrators, security teams, and developers using OverlayFS should assess exposure and verify Landlock configurations.
- Verify Landlock configurations to ensure proper access control for whiteout creation.
- Assess Linux kernel deployments using OverlayFS for potential exposure.
- Update to the latest kernel version if necessary to address vulnerability.
Technical summary
The Linux kernel vulnerability CVE-2026-89560 requires LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation in OverlayFS, addressing potential security concerns. This change guards whiteout creation via mknod(2) and renameat2(2) with RENAME_WHITEOUT, introducing a Landlock erratum for mknod(2) cases and fixing a bug in renameat2(2) handling. Linux kernel administrators, security teams, and developers using OverlayFS should assess exposure and verify Landlock configurations to ensure proper access control for whiteout creation.
Defensive priority
Verify Landlock configurations and assess exposure in Linux kernel deployments using OverlayFS.
Recommended defensive actions
- Review and update Landlock configurations to ensure proper access control for whiteout creation.
- Assess Linux kernel deployments using OverlayFS for potential exposure.
- Verify system configurations and update to the latest kernel version if necessary.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The CVE record and source metadata provide details on the Linux kernel vulnerability and its resolution. Evidence is limited to supplied source details, and defenders should verify Landlock configurations and assess exposure in Linux kernel deployments using OverlayFS. The vulnerability requires LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation, addressing potential security concerns.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-89560 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-89560
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-89560 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89560
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/0c3204aacbe8c07f9e87e3028f28ec6c166a1075
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/627ce4902df1d737e99306daae5a87c68b876d16
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/672fa082d48b21e1fb62cdb184fee41513e53421
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.