CVE-2026-43359

Summary

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.

Impact & exploitability

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products we track (1)

Recommendation

Apply the vendor fix in your normal patch cycle. Open any affected product above for its exact safe version.

Official patch: https://git.kernel.org/stable/c/2e57b8cac2ba0d38aac76c1ecdfd8b899e3581a5 ↗

Additional information

• NVD record
• https://git.kernel.org/stable/c/2e57b8cac2ba0d38aac76c1ecdfd8b899e3581a5Patch
• https://git.kernel.org/stable/c/41fb97353ff58fa4f31904c343fc8e3df2f7517dPatch
• https://git.kernel.org/stable/c/87f2c46003fce4d739138aab4af1942b1afdadacPatch
• https://git.kernel.org/stable/c/b19c0465e4daad5aa8f60552ea0578cf31a11b1ePatch
• https://git.kernel.org/stable/c/b9914db13ac15aca3b74544c0bb1a2e0dad1f174Patch
• https://git.kernel.org/stable/c/d11aefe654a04fc41996d254748d6a38b6b0a7bePatch