CVE-2026-80538: xfs: propagate errors from xfs_rtginode_load
In the Linux kernel, the following vulnerability has been resolved:
xfs: propagate errors from xfsrtginodeload
xfsrtginodeensure() treats every xfsrtginodeload() error other than -ENOENT as success. This can leave the realtime group inode unset after an I/O, allocation, or corruption error. Growfs then continues as though the inode had been loaded.
Only -ENOENT means that the inode needs to be created. Return all other errors to the growfs caller.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Which deployments are relevant to this issue?
The issue is relevant to XFS filesystems using realtime groups when a growfs operation causes the realtime group inode to be loaded. It is triggered when that load encounters an I/O, allocation, or filesystem-corruption error other than -ENOENT.
What error condition leads to unsafe growfs behavior?
Before the fix, xfs_rtginode_ensure() treated every xfs_rtginode_load() error except -ENOENT as success. This allowed growfs to continue even though the realtime group inode had not been set; -ENOENT is the only condition that should cause creation of the inode.