Full vulnerability report · 2026

CVE-2026-43053High confidence

xfs: close crash window in attr dabtree inactivation

Linux · Linux

4.7MediumCVSS 3.1

Recommended action

Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 22 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product

Operational reassessment

Published severity in operational context

Open reassessment dashboard →

Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

No CISA KEV confirmation is currently recorded.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.10% for the current model date.

Compensating controls

Validate the affected product branch and deploy the verified fixed release.
Restrict local access and enforce least privilege on affected hosts.
Monitor vendor guidance and exploitation sources for a material change.

Verification

Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 22 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Debian Security Tracker, Canonical Ubuntu Security: 22 affected package states with no published fix

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states

Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 22 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`linux`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · source	`linux`	Affected, no fix publishedDebian currently tracks this release as open.	`Not published in this feed`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.12-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · source	`linux`	Vendor fix publishedDebian records a fixed source-package version for this release.	`6.19.12-1`	Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical Ubuntu Security ↗Source updated 5 Oct 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

CVE-2026-43053 · CSAF 2.0 · revision 19 · interimSUSE Product Security TeamCVE-2026-43053

151 known affected

The vendor explicitly identifies these products as affected by this CVE.

kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4

Summary: 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.
Remediation: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".

Recommended actionPatch only the product branches with a verified fix

Fix availability varies by product

What, why and how

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.

What

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Time-of-check Time-of-use (TOCTOU) Race Condition → disrupt the affected service
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: High: exploitation depends on specific conditions
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-367 ↗
CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

Denial of serviceCWE-367

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-26652Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

BSI · German · WID-SEC-2026-1346Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.

Official advisory ↗

Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 May 2026, published on 6 May 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0956Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43024 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43034 https://www.cve.org/CVERecord?id=CVE-2026-43034 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43057 https://www.cve.org/CVERecord?id=CVE-2026-43057 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=CVE-2026-43081 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43086 https://www.cve.org/CVERecord?id=CVE-2026-43086 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43032 Référence CVE CVE-2026-43034 https://www.cve.org/CVERecord?id=CVE-2026-43034 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43043 https://www.cve.org/CVERecord?id=CVE-2026-43043 Référence CVE CVE-2026-43047 https://www.cve.org/CVERecord?id=CVE-2026-43047 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43057 https://www.cve.org/CVERecord?id=CVE-2026-43057 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43061 https://www.cve.org/CVERecord?id=CVE-2026-43061 Référence CVE CVE-2026-43062 https://www.cve.org/CVERecord?id=CVE-2026-43062 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0864Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43026 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43034 https://www.cve.org/CVERecord?id=CVE-2026-43034 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=CVE-2026-43049 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43059 https://www.cve.org/CVERecord?id=CVE-2026-43059 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=

Official advisory ↗

CERT-FR · French · CERTFR-2026-AVI-0833Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43024 Référence CVE CVE-2026-43026 https://www.cve.org/CVERecord?id=CVE-2026-43026 Référence CVE CVE-2026-43028 https://www.cve.org/CVERecord?id=CVE-2026-43028 Référence CVE CVE-2026-43030 https://www.cve.org/CVERecord?id=CVE-2026-43030 Référence CVE CVE-2026-43035 https://www.cve.org/CVERecord?id=CVE-2026-43035 Référence CVE CVE-2026-43036 https://www.cve.org/CVERecord?id=CVE-2026-43036 Référence CVE CVE-2026-43040 https://www.cve.org/CVERecord?id=CVE-2026-43040 Référence CVE CVE-2026-43049 https://www.cve.org/CVERecord?id=CVE-2026-43049 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43053 https://www.cve.org/CVERecord?id=CVE-2026-43053 Référence CVE CVE-2026-43054 https://www.cve.org/CVERecord?id=CVE-2026-43054 Référence CVE CVE-2026-43059 https://www.cve.org/CVERecord?id=CVE-2026-43059 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2026-014755LinuxのLinux KernelにおけるTime-of-check Time-of-use (TOCTOU) 競合状態の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。xfsにおけるattr dabtreeの非アクティブ化に伴うクラッシュウィンドウの閉鎖問題です。ノード形式の拡張属性を持つinodeを非アクティブ化する際、xfs_attr3_node_inactive()はxfs_trans_binval()を用いてすべての子のリーフおよびノードブロックを無効化しますが、親ノードブロックから対応するエントリを削除しません。この暗黙の前提は、xfs_attr_inactive()がその後attrフォーク全体をゼロエクステントに切り詰めるため、ログ回復時にルートノードに到達して古いポインタを追跡しないというものです。しかし、リーフおよびノードブロックの取消がコミットされた後、attr bmapの切り詰めがコミットされる前にログシャットダウンが発生した場合、この前提は崩れます。回復処理はattr bmapをそのまま再生します（inodeはまだattrフォークのエクステントを持っています）が、すべての取消されたリーフおよびノードブロックの再生を抑制し、それらがディスク上に古いデータとして残る可能性があります。次回のマウント時に、xlog_recover_process_iunlinks()は非アクティブ化を再試行し、attr bmap経由でルートノードを読み込もうとします。もしルートノードが再生されていなければ、読み込み時にすぐにメタデータ検証エラーが発生し、再生されていた場合でも、子ポインタをたどって未再生の子ブロックを読み込もうとして同じエラーが発生します。エラー例としては、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: ...、XFS (pmem0): metadata I/O error in "xfs_da_read_buf+0x104/0x190" at daddr 0x78 len 8 error 117があります。修正点は2箇所あります。1つ目は、xfs_attr3_node_inactive()内で子ブロックに対してxfs_trans_binval()を呼び出した後、同一トランザクション内で直ちに親ノードからその子ブロックを参照するエントリを削除し、親が取消されたブロックを指し示す期間を排除します。すべての子が削除された後、空になったルートノードは同じトランザクション内でリーフブロックに変換されます。このノードからリーフへの変換はクラッシュ安全性のために必要です。空のノードがログに書き込まれた後、第二段階のbmap切り詰めがコミットされる前にシステムシャットダウンが発生した場合、ログ回復はディスク上のルートブロックを検証しようとします。xfs_da3_node_verify()はcount == 0のノードブロックを許容しないため、そのようなブロックは検証に失敗しメタデータ破損シャットダウンを引き起こします。一方で、リーフブロックはこの一時的な状態を許容します。2つ目は、xfs_attr_inactive()内でattrフォークの切り詰めを2段階の明示的なフェーズに分割しました。まずルートブロックを超えるすべてのエクステント（親参照がすでに削除された子エクステント）を切り詰めます。次に、ルートブロックを無効化しattr bmapをゼロに切り詰める操作を単一トランザクションで行います。第二段階の2つの操作は原子で実行する必要があります。attr bmapに非ゼロ長が存在する限り、回復処理はそれを追跡してルートブロックに到達できるため、ルートブロックの無効化はbmapのゼロ切り詰めと同時にコミットされなければなりません。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Fix availability varies by product
Affected: kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5
kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5
ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
and 121 more
Fixed: Linux: < 2.6.12, 6.19.12 ≤ 6.19.*, 7.0 ≤ *
Action: Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 1 May 2026 · Last source change 11 May 2026, 22:16 UTC · CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2026-26652

Product sourceVendor CSAF · SUSE Product Security Team

Remediation sourceVendor CSAF · SUSE Product Security Team

CWE sourceNIST NVD

NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2026-05-01CVE published

2026-05-11Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-26652↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

xfs: close crash window in attr dabtree inactivation

Published severity in operational context

Evidence used

Compensating controls

Verification

Remediation availability differs by product scope

Release-specific package status

Authoritative vendor CSAF and VEX advisories

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2026-26652

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication