CVE-2026-43359btrfs: fix transaction abort on set received ioctl due to item overflow
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 – < b9914db13ac15aca3b74544c0bb1a2e0dad1f174
- affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 – < b19c0465e4daad5aa8f60552ea0578cf31a11b1e
- affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 – < 2e57b8cac2ba0d38aac76c1ecdfd8b899e3581a5
- affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 – < d11aefe654a04fc41996d254748d6a38b6b0a7be
- affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 – < 41fb97353ff58fa4f31904c343fc8e3df2f7517d
- affected dd5f9615fc5c5e8d3751aab3a17b92768fb1ce70 – < 87f2c46003fce4d739138aab4af1942b1afdadac
- affected 3.12
- unaffected < 3.12
- unaffected 6.1.167 – ≤ 6.1.*
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.18.19 – ≤ 6.18.*
- unaffected 6.19.9 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/b9914db13ac15aca3b74544c0bb1a2e0dad1f174 (opens in a new tab)
- https://git.kernel.org/stable/c/b19c0465e4daad5aa8f60552ea0578cf31a11b1e (opens in a new tab)
- https://git.kernel.org/stable/c/2e57b8cac2ba0d38aac76c1ecdfd8b899e3581a5 (opens in a new tab)
- https://git.kernel.org/stable/c/d11aefe654a04fc41996d254748d6a38b6b0a7be (opens in a new tab)
- https://git.kernel.org/stable/c/41fb97353ff58fa4f31904c343fc8e3df2f7517d (opens in a new tab)
- https://git.kernel.org/stable/c/87f2c46003fce4d739138aab4af1942b1afdadac (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-28665 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43359)Record last updated .