Skip to main content

Linux Kernel XFS EUVDEUVD-2026-27712

| CVE-2026-43153 HIGH
Use After Free (CWE-416)
2026-05-06 Linux GHSA-j9jf-6fw4-2v2v
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain local user account
  2. Delivery
    Invoke XFS extended attribute syscalls
  3. Exploit
    Trigger specific xfs_attr3_leaf_lookup_int error path
  4. Install
    Cause use-after-free with dangling buffer pointer
  5. C2
    Groom kernel heap memory
  6. Execute
    Overwrite freed buffer with controlled data
  7. Impact
    Trigger pointer dereference
  8. Step 8
    Execute arbitrary kernel code
  9. Step 9
    Escalate to root privileges

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires authenticated local user access with low-privilege account (PR:L) on a Linux system running kernel versions 5.9 through unpatched 6.x/7.x series. Specifically requires the XFS filesystem to be mounted and in use - systems using only ext4, btrfs, or other filesystems are not affected. Exploitation depends on triggering XFS extended attribute operations (xattr syscalls such as setxattr, getxattr, listxattr, or removexattr) that invoke the vulnerable xfs_attr_leaf_hasname() code path with specific error conditions from xfs_attr3_leaf_lookup_int. The attacker must cause error returns other than -ENOATTR or -EEXIST to trigger the dangling pointer condition. Attack complexity is low (AC:L) but successful privilege escalation requires kernel exploitation expertise to reliably control freed memory and achieve code execution. Remote exploitation is not possible (AV:L) - network access alone is insufficient. Systems that do not grant local shell access to untrusted users, or that use filesystems other than XFS, are not practically exploitable regardless of kernel version.

Impact

The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates local access with low complexity and low privileges required, enabling high impact across confidentiality, integrity, and availability. However, real-world risk signals are mixed. The EPSS score of 0.02% (5th percentile) suggests extremely low observed exploitation probability in the wild. No CISA KEV listing exists, indicating no confirmed active exploitation. The local attack vector (AV:L) significantly limits exposure compared to network-accessible vulnerabilities - an attacker must already have authenticated shell access to the target system. The low privilege requirement (PR:L) means any local user account suffices, but the attacker cannot be completely unprivileged. The vulnerability affects kernel memory management in XFS extended attribute operations, which are not constantly exercised in typical workloads, further reducing attack surface. While kernel use-after-free vulnerabilities theoretically enable privilege escalation to root, successful exploitation requires precise memory manipulation and timing. For organizations not using XFS filesystems or not granting local shell access to untrusted users, practical risk is minimal despite the high CVSS score. Priority should be moderate - patch during normal maintenance windows unless XFS is used on multi-tenant systems with local user access.

Exploit ScenarioDerived

An attacker with a low-privilege local account on a Linux system using XFS filesystem performs extended attribute operations designed to trigger error conditions in xfs_attr3_leaf_lookup_int. By carefully crafting attribute names or manipulating filesystem state to cause specific error codes (excluding -ENOATTR and -EEXIST), the attacker triggers the use-after-free condition where xfs_attr_leaf_hasname returns a pointer to freed buffer memory. The attacker then leverages heap grooming techniques to control the freed memory region and writes malicious data structures into it. When the kernel subsequently dereferences the dangling pointer, it executes attacker-controlled code with kernel privileges, escalating from limited user access to root-level system compromise. No public proof-of-concept is currently identified, and low EPSS score suggests successful exploitation requires significant technical expertise.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 08, 2026

A use-after-free flaw in the Linux kernel XFS filesystem's xfs_attr_leaf_hasname() function allows local authenticated attackers to potentially execute arbitrary code with kernel privileges or cause denial of service. The function's problematic calling convention can return a pointer to an already-released buffer when xfs_attr3_leaf_lookup_int fails with specific error codes, creating a memory safety issue. Despite a CVSS score of 7.8, EPSS indicates only 0.02% probability of exploitation (5th percentile), suggesting low real-world targeting. Vendor patches are available across multiple stable kernel versions (6.12.75, 6.18.16, 6.19.6, 7.0), and the fix has been committed upstream.

RemediationAI

Organizations should upgrade to patched Linux kernel versions: 6.12.75, 6.18.16, 6.19.6, or 7.0 depending on their stable branch. Distribution-specific kernel updates should be applied through normal package management channels (apt, yum, dnf) as vendors backport the fix. The upstream patches are available at git.kernel.org stable tree commits referenced in NVD. If immediate patching is not feasible, consider these compensating controls with their trade-offs: disable XFS filesystem usage and migrate data to ext4 or another filesystem (significant operational disruption and data migration risk), restrict local shell access to only trusted administrative accounts through PAM configuration and disable user account creation (reduces attack surface but may break legitimate workflows requiring local access), or implement kernel lockdown mode with module signing enforcement to prevent exploitation attempts that rely on loading malicious kernel modules (may break compatibility with some third-party drivers). Note that workarounds only reduce attack surface - they do not eliminate the kernel vulnerability. The memory safety fix requires kernel patching. After applying updates, reboot systems to load the patched kernel. Verify running kernel version with uname -r command.

Affected VersionsENISA

Linux patch: 6.19.6
Linux 07120f1abdff80f3d1351f733661abe28d609535 <457121c01f609b9934addbb04d5c1ef638c71c61
Linux patch: 0
Linux patch: 6.12.75
Linux patch: 6.18.16
Linux 07120f1abdff80f3d1351f733661abe28d609535 <530082df991903f3330354e99e0cb7b05debfa86
Linux patch: 7.0
Linux 07120f1abdff80f3d1351f733661abe28d609535 <3a65ea768b8094e4699e72f9ab420eb9e0f3f568
Linux 5.9
Linux 07120f1abdff80f3d1351f733661abe28d609535 <2fbc8421d1db102c0e5458607e042a23a03648b1

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability exists in the XFS filesystem's extended attribute handling code, specifically in the xfs_attr_leaf_hasname() helper function within the Linux kernel. XFS extended attributes store metadata about files and directories in leaf nodes. The problematic function has inconsistent buffer management behavior: it returns NULL when xfs_attr3_leaf_read() fails, returns a valid buffer on -ENOATTR or -EEXIST from xfs_attr3_leaf_lookup_int(), but critically returns a dangling pointer to freed memory when xfs_attr3_leaf_lookup_int() fails with other error codes. This creates a use-after-free condition where callers may attempt to access already-deallocated buffer memory. The CPE data identifies this affecting the core Linux kernel package (cpe:2.3:a:linux:linux). The fix involves removing the problematic abstraction and open-coding the logic in callers to ensure each caller properly manages buffer lifecycle after xfs_attr3_leaf_read().

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SUSE HIGH
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
May 08, 2026 - 13:22 NVD
7.8 (HIGH)
Patch available
May 06, 2026 - 13:32 EUVD
CVE Published
May 06, 2026 - 11:27 nvd
HIGH 7.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

xfs: remove xfs_attr_leaf_hasname

The calling convention of xfs_attr_leaf_hasname() is problematic, because it returns a NULL buffer when xfs_attr3_leaf_read fails, a valid buffer when xfs_attr3_leaf_lookup_int returns -ENOATTR or -EEXIST, and a non-NULL buffer pointer for an already released buffer when xfs_attr3_leaf_lookup_int fails with other error values.

Fix this by simply open coding xfs_attr_leaf_hasname in the callers, so that the buffer release code is done by each caller of xfs_attr3_leaf_read.

Executive ViewAI

Why It Matters

CVE-2026-43153 is a use-after-free vulnerability in the Linux kernel XFS filesystem that could allow authenticated local users to execute arbitrary code with kernel privileges or trigger system crashes. While the CVSS score is 7.8, real-world exploitation probability is extremely low (0.02%), and vendor patches are already available across supported kernel versions, reducing immediate organizational risk for patched systems.

Business Impact: Medium
Compensating Controls

Apply vendor patch. Interim mitigations pending patch deployment: restrict local system access to trusted users only; disable XFS attribute operations where operationally feasible; monitor kernel logs for xfs_attr-related errors indicating exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: High
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy