CVE-2026-43118: btrfs: fix zero size inode with non-zero size after log replay
btrfs: fix zero size inode with non-zero size after log replay
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.19.14-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.24 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.19.14
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43118?
CVE-2026-43118 has been rated as a low severity vulnerability affecting btrfs in the Linux kernel.
How do I fix CVE-2026-43118?
To resolve CVE-2026-43118, you should update to the latest version of the Linux kernel that includes the fix.
What does CVE-2026-43118 affect?
CVE-2026-43118 affects the btrfs filesystem implementation in the Linux kernel.
Is CVE-2026-43118 exploitable?
CVE-2026-43118 is not expected to be exploitable in practical scenarios but may lead to filesystem anomalies.
Which versions of the Linux kernel are affected by CVE-2026-43118?
Versions of the Linux kernel from 2.6.30 to 6.19 and 7.0-rc1 to 7.0-rc5 are affected by CVE-2026-43118.