CVE-2026-43118: btrfs: fix zero size inode with non-zero size after log replay
Published May 6, 2026
·Updated
btrfs: fix zero size inode with non-zero size after log replay
Affected Software
8 affected components
Linux btrfs (Linux kernel)
Linux Linux kernel>=2.6.30<6.18.24
Linux Linux kernel>=6.19<6.19.14
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Event History
May 6, 2026
CVE Published
via MITRE·07:40 AM
Data Sourced
via MITRE·07:40 AM
Description
Data Sourced
via NVD·10:16 AM
RemedyDescriptionSeverityAffected Software
May 7, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
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.
2
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.
3
What does CVE-2026-43118 affect?
CVE-2026-43118 affects the btrfs filesystem implementation in the Linux kernel.
4
Is CVE-2026-43118 exploitable?
CVE-2026-43118 is not expected to be exploitable in practical scenarios but may lead to filesystem anomalies.
5
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.