btrfs: fix transaction abort on set received ioctl due to item overflow
Summary
| CVE | CVE-2026-43359 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-08 15:16:46 UTC |
| Updated | 2026-05-12 14:10:27 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: btrfs: fix transaction abort on set received ioctl due to item overflow If the set received ioctl fails due to an item overflow when attempting to add the BTRFS_UUID_KEY_RECEIVED_SUBVOL we have to abort the transaction since we did some metadata updates before. This means that if a user calls this ioctl with the same received UUID field for a lot of subvolumes, we will hit the overflow, trigger the transaction abort and turn the filesystem into RO mode. A malicious user could exploit this, and this ioctl does not even requires that a user has admin privileges (CAP_SYS_ADMIN), only that he/she owns the subvolume. Fix this by doing an early check for item overflow before starting a transaction. This is also race safe because we are holding the subvol_sem semaphore in exclusive (write) mode. A test case for fstests will follow soon. |
Risk And Classification
EPSS: 0.000240000 probability, percentile 0.070360000 (date 2026-05-12)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 b9914db13ac15aca3b74544c0bb1a2e0dad1f174 git | Not specified |
| CNA | Linux | Linux | affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 b19c0465e4daad5aa8f60552ea0578cf31a11b1e git | Not specified |
| CNA | Linux | Linux | affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 2e57b8cac2ba0d38aac76c1ecdfd8b899e3581a5 git | Not specified |
| CNA | Linux | Linux | affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 d11aefe654a04fc41996d254748d6a38b6b0a7be git | Not specified |
| CNA | Linux | Linux | affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 41fb97353ff58fa4f31904c343fc8e3df2f7517d git | Not specified |
| CNA | Linux | Linux | affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 87f2c46003fce4d739138aab4af1942b1afdadac git | Not specified |
| CNA | Linux | Linux | affected 3.12 | Not specified |
| CNA | Linux | Linux | unaffected 3.12 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.130 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.78 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.19 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.9 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/d11aefe654a04fc41996d254748d6a38b6b0a7be | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2e57b8cac2ba0d38aac76c1ecdfd8b899e3581a5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b19c0465e4daad5aa8f60552ea0578cf31a11b1e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/87f2c46003fce4d739138aab4af1942b1afdadac | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b9914db13ac15aca3b74544c0bb1a2e0dad1f174 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/41fb97353ff58fa4f31904c343fc8e3df2f7517d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.