Skip to main content

Linux Kernel EUVDEUVD-2026-26652

| CVE-2026-43053 MEDIUM
Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)
2026-05-01 Linux
4.7
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Recon
    Write extended attributes to XFS inode
  2. Delivery
    Trigger inode inactivation via unlinking
  3. Exploit
    Initiate log shutdown mid-inactivation
  4. Install
    Restart filesystem
  5. C2
    Attempt root block read during recovery
  6. Execute
    Follow stale child pointers
  7. Impact
    Metadata verification failure

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
Exploitation Conditions

The vulnerability is triggered only when the following specific conditions align: (1) the XFS filesystem is in active use with node-format extended attributes on at least one inode (attribute B-tree has multiple levels, not a leaf block); (2) an inode with such attributes is being inactivated (removed or evicted); (3) a log shutdown occurs after xfs_attr3_node_inactive() completes child block invalidation but before xfs_attr_inactive() completes the second-phase attribute fork truncation to zero extents; (4) the kernel crashes or is forcibly restarted between these two commit points. No special configuration is required beyond having XFS enabled and attribute B-tree depth greater than one. Exploitation is limited by the narrow timing window (high AC in CVSS) and requirement for unplanned shutdown during the specific inactivation window, making this operationally significant but not practically weaponizable by remote or unprivileged attackers.

Impact

Despite the moderate CVSS score of 4.7, real-world risk is notably constrained by multiple factors. The CVSS vector (AV:L/AC:H/PR:L) indicates local access with high complexity and low privilege requirements, limiting the threat model to authenticated users with filesystem write access. The EPSS score of 0.02% (5th percentile) reflects extremely low exploitation probability, suggesting this is not a practical attack vector despite the availability of the triggering scenario. Active exploitation is not confirmed; no CISA KEV entry or public POC is mentioned. The impact is strictly denial of service (filesystem unavailability requiring manual repair), not escalation or data exposure. However, this vulnerability has legitimate operational concern: any XFS user running an older kernel during extended attribute operations faces non-zero risk of unplanned downtime if power loss or other force shutdown occurs. The high AC (Complexity) rating likely reflects the difficulty of reliably triggering the narrow window between block invalidation and truncation completion. For critical infrastructure using XFS, timely patching mitigates a low-probability but operationally significant failure mode.

Exploit ScenarioDerived

An authenticated user with write access to an XFS filesystem with node-format extended attributes (many attributes or large attribute values) performs attribute operations (setxattr syscalls). An attacker or simulated failure induces a log shutdown (via power loss, forced reboot, or kernel panic) precisely between the point where child blocks are invalidated and the attribute fork is truncated to zero. On next mount, log recovery replays the stale parent-node references but suppresses the child block metadata, and xlog_recover_process_iunlinks() crashes when attempting to follow these pointers during inode inactivation, rendering the filesystem unmount-required. Exploitation requires precise timing (high complexity) but does not require elevated privileges beyond filesystem write access.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 07, 2026

XFS filesystem crashes during log recovery when inodes with node-format extended attributes are inactivated following an untimely log shutdown, due to stale metadata block references in the attribute B-tree. Unprivileged local attackers with write access to XFS filesystems can trigger this denial-of-service condition by inducing log shutdown during extended attribute cleanup, causing the filesystem to unmount and require repair. The vulnerability affects Linux kernel versions prior to 6.19.12 and later stable branches.

RemediationAI

Patch immediately to Linux kernel version 6.19.12 or later, or apply the upstream commits e5a3e3cdd9b3015ae79456c81beebfdbb5246c0f and b854e1c4eff3473b6d3a9ae74129ac5c48bc0b61 (https://git.kernel.org/stable/c/e5a3e3cdd9b3015ae79456c81beebfdbb5246c0f and https://git.kernel.org/stable/c/b854e1c4eff3473b6d3a9ae74129ac5c48bc0b61). For systems unable to update immediately, mitigate risk by ensuring stable power supply and avoiding unplanned shutdowns during extended attribute operations on XFS filesystems. If filesystem corruption is detected (XFS metadata corruption errors during mount), run xfs_repair to restore filesystem integrity before resuming operations. Long-term, maintain consistent kernel patching cadence and monitor xfs/attr-related fixes in stable kernel releases.

Affected VersionsENISA

Linux patch: 0
Linux patch: 6.19.12
Linux 2.6.12
Linux patch: 7.0
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b854e1c4eff3473b6d3a9ae74129ac5c48bc0b61
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e5a3e3cdd9b3015ae79456c81beebfdbb5246c0f

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

The XFS filesystem manages extended attributes using a B-tree (dabtree) structure. When an inode with node-format attributes is being inactivated (removed), the kernel invalidates child leaf and node blocks via xfs_trans_binval() while keeping parent node references intact, relying on a subsequent attribute fork truncation to clean up the entire structure. However, a crash window exists between block invalidation and fork truncation. If a log shutdown occurs during this window, log recovery replays the attribute fork extent map but suppresses replay of the cancelled child blocks, leaving stale pointers in parent nodes. During subsequent mount and inode inactivation retry, xlog_recover_process_iunlinks() attempts to follow these invalid pointers, triggering XFS metadata verification failures (CWE-367: Time-of-check Time-of-use race condition). The fix involves two coordination points: immediate parent reference removal after each child block invalidation in xfs_attr3_node_inactive(), and atomic two-phase attribute fork truncation in xfs_attr_inactive() to ensure the root block invalidation and bmap truncation commit together.

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

NVD PRIMARY 4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM
Red Hat 5.5 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

3
CVSS changed
May 07, 2026 - 18:37 NVD
4.7 (MEDIUM)
CVE Published
May 01, 2026 - 14:15 nvd
MEDIUM 4.7
CVE Published
May 01, 2026 - 14:15 nvd
N/A

DescriptionNVD

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

xfs: close crash window in attr dabtree inactivation

When inactivating an inode with node-format extended attributes, xfs_attr3_node_inactive() invalidates all child leaf/node blocks via xfs_trans_binval(), but intentionally does not remove the corresponding entries from their parent node blocks. The implicit assumption is that xfs_attr_inactive() will truncate the entire attr fork to zero extents afterwards, so log recovery will never reach the root node and follow those stale pointers.

However, if a log shutdown occurs after the leaf/node block cancellations commit but before the attr bmap truncation commits, this assumption breaks. Recovery replays the attr bmap intact (the inode still has attr fork extents), but suppresses replay of all cancelled leaf/node blocks, maybe leaving them as stale data on disk. On the next mount, xlog_recover_process_iunlinks() retries inactivation and attempts to read the root node via the attr bmap. If the root node was not replayed, reading the unreplayed root block triggers a metadata verification failure immediately; if it was replayed, following its child pointers to unreplayed child blocks triggers the same failure:

XFS (pmem0): Metadata corruption detected at xfs_da3_node_read_verify+0x53/0x220, xfs_da3_node block 0x78 XFS (pmem0): Unmount and run xfs_repair XFS (pmem0): First 128 bytes of corrupted metadata buffer: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ XFS (pmem0): metadata I/O error in "xfs_da_read_buf+0x104/0x190" at daddr 0x78 len 8 error 117

Fix this in two places:

In xfs_attr3_node_inactive(), after calling xfs_trans_binval() on a child block, immediately remove the entry that references it from the parent node in the same transaction. This eliminates the window where the parent holds a pointer to a cancelled block. Once all children are removed, the now-empty root node is converted to a leaf block within the same transaction. This node-to-leaf conversion is necessary for crash safety. If the system shutdown after the empty node is written to the log but before the second-phase bmap truncation commits, log recovery will attempt to verify the root block on disk. xfs_da3_node_verify() does not permit a node block with count == 0; such a block will fail verification and trigger a metadata corruption shutdown. on the other hand, leaf blocks are allowed to have this transient state.

In xfs_attr_inactive(), split the attr fork truncation into two explicit phases. First, truncate all extents beyond the root block (the child extents whose parent references have already been removed above). Second, invalidate the root block and truncate the attr bmap to zero in a single transaction. The two operations in the second phase must be atomic: as long as the attr bmap has any non-zero length, recovery can follow it to the root block, so the root block invalidation must commit together with the bmap-to-zero truncation.

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Medium

Priority Score

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

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Vendor StatusVendor

SUSE

Severity: Medium
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