CVE-2026-80538 (GCVE-0-2026-80538)
Vulnerability from cvelistv5
Published
2026-08-26 14:37
Modified
2026-08-27 05:01
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
xfs: propagate errors from xfs_rtginode_load
xfs_rtginode_ensure() treats every xfs_rtginode_load() 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.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/xfs/xfs_rtalloc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "ec19cea4ef1ce9d6e2e3f7e9e7bf88ede31176e7",
"status": "affected",
"version": "ae897e0bed0f5461a6b1c3259c7d899759ba2a62",
"versionType": "git"
},
{
"lessThan": "61c5165f02deb2eed9b6b539bb279e6629fee652",
"status": "affected",
"version": "ae897e0bed0f5461a6b1c3259c7d899759ba2a62",
"versionType": "git"
},
{
"lessThan": "b7e53968cb8882c2d276429ea8550848a4940874",
"status": "affected",
"version": "ae897e0bed0f5461a6b1c3259c7d899759ba2a62",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/xfs/xfs_rtalloc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.13"
},
{
"lessThan": "6.13",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.46",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.10",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.46",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.10",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "6.13",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: propagate errors from xfs_rtginode_load\n\nxfs_rtginode_ensure() treats every xfs_rtginode_load() error other than\n-ENOENT as success. This can leave the realtime group inode unset after an\nI/O, allocation, or corruption error. Growfs then continues as though the\ninode had been loaded.\n\nOnly -ENOENT means that the inode needs to be created. Return all other\nerrors to the growfs caller."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.1,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The bug is reached only through the local XFS_IOC_FSGROWFSRT ioctl (xfs_file_ioctl -\u003e xfs_growfs_rt -\u003e xfs_growfs_rtg -\u003e xfs_rtginode_ensure); it is not exposed via NFS, ksmbd, or any network packet handler.\nAC:L - A growfs caller can reliably force xfs_rtginode_load() to return a non-ENOENT error using attacker-influenced conditions such as memory pressure, RT device/metadata I/O faults, or corrupted rtgroup inode state, deterministically entering the swallowed-error path.\nPR:L - xfs_growfs_rt() gates on capable(CAP_SYS_ADMIN), which is satisfied by user-namespace root per kernel CNA guidance; only a writable file descriptor on a realtime-enabled XFS mount is additionally required, not init-namespace root.\nUI:N - The attacker with the required capability and mount write access issues XFS_IOC_FSGROWFSRT directly; no separate victim action such as opening files or mounting the filesystem is needed beyond that.\nS:U - Impact is a host kernel crash or on-disk XFS realtime metadata corruption within the same kernel security domain; it does not cross a VM, container, or IOMMU isolation boundary.\nC:N - The failure mode is an unset rtgroup inode pointer followed by NULL xfs_inode dereference during growfs; there is no use-after-free, out-of-bounds read, or other kernel memory disclosure primitive.\nI:H - Continuing growfs after rtgroup inode load failures lets superblock and realtime bitmap/summary update paths proceed while critical metadata inodes were never loaded, corrupting on-disk XFS realtime metadata integrity (notably on zoned growfs paths that can commit before crashing).\nA:H - When growfs proceeds with NULL rtgroup bitmap or summary inodes, xfs_growfs_rt_bmblock and xfs_rtfile_initialize_blocks dereference the missing xfs_inode and trigger a kernel oops or panic, denying system availability."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-27T05:01:28.422Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/ec19cea4ef1ce9d6e2e3f7e9e7bf88ede31176e7"
},
{
"url": "https://git.kernel.org/stable/c/61c5165f02deb2eed9b6b539bb279e6629fee652"
},
{
"url": "https://git.kernel.org/stable/c/b7e53968cb8882c2d276429ea8550848a4940874"
}
],
"title": "xfs: propagate errors from xfs_rtginode_load",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-80538",
"datePublished": "2026-08-26T14:37:12.767Z",
"dateReserved": "2026-08-26T14:34:25.765Z",
"dateUpdated": "2026-08-27T05:01:28.422Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…