{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80538 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-80538 is a high-severity vulnerability in Linux, published on 26 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-80538 and fix it if it is affected.\n\nWhat it is: CVE-2026-80538 is a high-severity vulnerability in Linux, published on 26 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-80538 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80538/ (Markdown: https://insights.sbomify.com/CVE-2026-80538/index.md)","id":"CVE-2026-80538","markdown":"https://insights.sbomify.com/CVE-2026-80538/index.md","name":"CVE-2026-80538","record":{"aliases":["BELL-CVE-2026-80538","DEBIAN-CVE-2026-80538","GHSA-5q37-jjr8-c4m5","UBUNTU-CVE-2026-80538"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"xfs: propagate errors from xfs_rtginode_load","id":"CVE-2026-80538","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"drm/amdgpu: disallow multiple FENCE chunks in one submit","id":"CVE-2026-80539"},"packages":[],"prev":{"headline":"xfs: fix off-by-one in rtrefcount btree root level validation","id":"CVE-2026-80537"},"products":["Linux"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-27","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-80538/"}