CVE-2025-68736: landlock: Fix handling of disconnected directories
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 426d5b681b2f3339ff04da39b81d71176dc8c87c, 49c9e09d961025b22e61ef9ad56aa1c21b6ce2f1, 4f5cdc82a6c7e22cfd9a92d203cec13a52a3f363; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1.
Low priority for now. Upgrade to Linux Linux 426d5b681b2f3339ff04da39b81d71176dc8c87c, 49c9e09d961025b22e61ef9ad56aa1c21b6ce2f1, 4f5cdc82a6c7e22cfd9a92d203cec13a52a3f363; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: landlock: Fix handling of disconnected directories Disconnected files or directories can appear when they are visible and opened from a bind mount, but have been renamed or moved from the source of the bind mount in a way that makes them inaccessible from the mount point (i.e. out of scope). Previously, access rights tied to files or directories opened through a disconnected directory were collected by walking the related hierarchy down to the root of the filesystem, without taking into account the mount point because it couldn't be found. This could lead to inconsistent access results, potential access right widening, and hard-to-debug renames, especially since such paths cannot be printed. For a sandboxed task to create a disconnected directory, it needs to have write access (i.e. FS_MAKE_REG, FS_REMOVE_FILE, and FS_REFER) to the underlying source of the bind mount, and read access to the related mount point. Because a sandboxed task cannot acquire more access rights than those defined by its Landlock domain, this could lead to inconsistent access rights due to missing permissions that should be inherited from the mount point hierarchy, while inheriting permissions from the filesystem hierarchy hidden by this mount point instead. Landlock now handles files and directories opened from disconnected directories by taking into account the filesystem hierarchy when the mount point is not found in the hierarchy walk, and also always taking into account the mount point from which these disconnected directories were opened. This ensures that a rename is not allowed if it would widen access rights [1]. The rationale is that, even if disconnected hierarchies might not be visible or accessible to a sandboxed task, relying on the collected access rights from them improves the guarantee that access rights will not be widened during a rename because of the access right comparison between the source and the destination (see LANDLOCK_ACCESS_FS_REFER). It may look like this would grant more access on disconnected files and directories, but the security policies are always enforced for all the evaluated hierarchies. This new behavior should be less surprising to users and safer from an access control perspective. Remove a wrong WARN_ON_ONCE() canary in collect_domain_accesses() and fix the related comment. Because opened files have their access rights stored in the related file security properties, there is no impact for disconnected or unlinked files.
- Published
- Dec 24, 2025
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.13affected
- cb2c7d1a1776057c9a1f48ed1250d85e94d4850d and later · before 4f5cdc82a6c7e22cfd9a92d203cec13a52a3f363affected · git
- cb2c7d1a1776057c9a1f48ed1250d85e94d4850d and later · before fbf718d5afe21057694a0c0223a18b0c7a5960b6affected · git
- cb2c7d1a1776057c9a1f48ed1250d85e94d4850d and later · before 426d5b681b2f3339ff04da39b81d71176dc8c87caffected · git
- cb2c7d1a1776057c9a1f48ed1250d85e94d4850d and later · before cadb28f8b3fd6908e3051e86158c65c3a8e1c907affected · git
- cb2c7d1a1776057c9a1f48ed1250d85e94d4850d and later · before 49c9e09d961025b22e61ef9ad56aa1c21b6ce2f1affected · git
- before 5.13not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.143 and later · up to and including 6.6.*not affected · semver
- 6.12.80 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.18.3-1 | 6.18.3-1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_10 | before 1-150700.15.3.1 | 1-150700.15.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_10 | before 1-150700.1.3.1 | 1-150700.1.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-64kb | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-default | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-default-base | before 6.4.0-150700.53.34.1.150700.17.23.1 | 6.4.0-150700.53.34.1.150700.17.23.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-source | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | kernel-zfcpdump | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | kernel-docs | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | kernel-obs-build | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP7 | kernel-syms | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP7 | kernel-azure | before 6.4.0-150700.53.34.1 | 6.4.0-150700.53.34.1 |
| SUSE:Linux Micro 6.1 | kernel-default | before 6.4.0-40.1 | 6.4.0-40.1 |
| SUSE:Linux Micro 6.1 | kernel-default-base | before 6.4.0-40.1.21.17 | 6.4.0-40.1.21.17 |
| SUSE:Linux Micro 6.1 | kernel-kvmsmall | before 6.4.0-40.1 | 6.4.0-40.1 |
| SUSE:Linux Micro 6.1 | kernel-source | before 6.4.0-40.1 | 6.4.0-40.1 |
| SUSE:Real Time Module 15 SP7 | kernel-rt | before 6.4.0-150700.7.34.1 | 6.4.0-150700.7.34.1 |
| SUSE:Real Time Module 15 SP7 | kernel-source-rt | before 6.4.0-150700.7.34.1 | 6.4.0-150700.7.34.1 |
| SUSE:Real Time Module 15 SP7 | kernel-syms-rt | before 6.4.0-150700.7.34.1 | 6.4.0-150700.7.34.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54156Dec 24, 2025 · sfc: fix crash when reading stats while NIC is resetting31Monitor
- ← EarlierCVE-2025-68735Dec 24, 2025 · drm/panthor: Prevent potential UAF in group creation31Monitor
- Later →CVE-2025-68737Dec 24, 2025 · arm64/pageattr: Propagate return value from __change_memory_common0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 426d5b681b2f3339ff04da39b81d71176dc8c87c | Vendor (CNA) |
| Linux Linux | 49c9e09d961025b22e61ef9ad56aa1c21b6ce2f1 | Vendor (CNA) |
| Linux Linux | 4f5cdc82a6c7e22cfd9a92d203cec13a52a3f363 | Vendor (CNA) |
| Linux Linux | cadb28f8b3fd6908e3051e86158c65c3a8e1c907 | Vendor (CNA) |
| Linux Linux | fbf718d5afe21057694a0c0223a18b0c7a5960b6 | Vendor (CNA) |
| azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150700.53.34.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150700.53.34.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150700.53.34.1.150700.17.23.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-docs | 6.4.0-150700.53.34.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_10 | 1-150700.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-obs-build | 6.4.0-150700.53.34.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150700.7.34.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-150700.53.34.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-150700.7.34.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-syms | 6.4.0-150700.53.34.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7 | Package registry (OSV) |
| suse:kernel-syms-rt | 6.4.0-150700.7.34.1 · SUSE:Real Time Module 15 SP7 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.4.0-150700.53.34.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.