Vulnerability · Published May 6, 2026 · Assigned by Linux

CVE-2026-43187xfs: delete attr leaf freemap entries when empty

High 8.8

In plain English

A high-severity integer overflow in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 41% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.8High
Exploit odds (30 days)0.5%top 59.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: xfs: delete attr leaf freemap entries when empty Back in commit 2a2b5932db6758 ("xfs: fix attr leaf header freemap.size underflow"), Brian Foster observed that it's possible for a small freemap at the end of the end of the xattr entries array to experience a size underflow when subtracting the space consumed by an expansion of the entries array. There are only three freemap entries, which means that it is not a complete index of all free space in the leaf block. This code can leave behind a zero-length freemap entry with a nonzero base. Subsequent setxattr operations can increase the base up to the point that it overlaps with another freemap entry. This isn't in and of itself a problem because the code in _leaf_add that finds free space ignores any freemap entry with zero size. However, there's another bug in the freemap update code in _leaf_add, which is that it fails to update a freemap entry that begins midway through the xattr entry that was just appended to the array. That can result in the freemap containing two entries with the same base but different sizes (0 for the "pushed-up" entry, nonzero for the entry that's actually tracking free space). A subsequent _leaf_add can then allocate xattr namevalue entries on top of the entries array, leading to data loss. But fixing that is for later. For now, eliminate the possibility of confusion by zeroing out the base of any freemap entry that has zero size. Because the freemap is not intended to be a complete index of free space, a subsequent failure to find any free space for a new xattr will trigger block compaction, which regenerates the freemap. It looks like this bug has been in the codebase for quite a long time.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.170-1DEBIAN-CVE-2026-43187
Debian:13linux6.12.85-1DEBIAN-CVE-2026-43187
Debian:14linux6.19.6-1DEBIAN-CVE-2026-43187
Ubuntu:22.04:LTSlinux5.15.0-186.196UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux6.8.0-134.134UBUNTU-CVE-2026-43187
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-aws5.15.0-1112.119UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-aws6.8.0-1060.63UBUNTU-CVE-2026-43187
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure5.15.0-1117.126UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure6.8.0-1063.71UBUNTU-CVE-2026-43187
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1117.126UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1062.69UBUNTU-CVE-2026-43187
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-gcp5.15.0-1112.122UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-gcp6.8.0-1063.69UBUNTU-CVE-2026-43187
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-gke5.15.0-1108.114UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-gke6.8.0-1058.64UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1095.103UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1045.48UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-ibm5.15.0-1106.110UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-ibm6.8.0-1060.61UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1060.61~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1107.113UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-kvm5.15.0-1104.109UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-184.194UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-134.134.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-134.134.1~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1107.108UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1058.61UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1058.61.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1064.66UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1029.30UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1053.53UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-oracle5.15.0-1109.115UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-oracle6.8.0-1057.58UBUNTU-CVE-2026-43187
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1057.58~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-raspi5.15.0-1106.109UBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-raspi6.8.0-1060.64UBUNTU-CVE-2026-43187
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43187
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43187
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-134.134~22.04.1UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-43187
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1032.33UBUNTU-CVE-2026-43187
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1075.79UBUNTU-CVE-2026-43187

Affected products (as reported)

VendorProductVersions
Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before f3c0d1fc1eadbb4adbee5ab7757d41d35f48325b1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before aa9083d97e2157da3c6fb45ddb1a97af7f188f7f1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before a631899025d47ea1aa6464d76db5b4d3b6d196fd1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before ffaf5c99d0f862db021fb1af8b813c1416b1beb21da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before e1b8c6452ee99a30e188a88f3f3f804fb1c6004a1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before f31a8334e1c54b126fcecf98645a49b6bc5ad3991da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 479b05fc3ee272090f671b06a41f3da8aa78eece1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 6f13c1d2a6271c2e73226864a0e83de2770b6f34
Linux Linux 2.6.12

Weakness: CWE-190 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References