{"api_version":"1","generated_at":"2026-11-20T20:06:31+00:00","cve":"CVE-2026-99412","urls":{"html":"https://cve.report/CVE-2026-99412","api":"https://cve.report/api/cve/CVE-2026-99412.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99412","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99412"},"summary":{"title":"xfs: avoid cross-rtgroup reaping after a repair","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: avoid cross-rtgroup reaping after a repair\n\nLOLLM notices that the extents stored in a xrtb_bitmap (aka xfs_rtblock\nbitmap) can span multiple rtgroups due to two circumstances.  The first\nis that the size of an rtgroup is an exact power of two, which means\nthat rtgroups are adjacent in the segmented xfs_rtblock_t address space.\nThis is fairly common to reduce the amount of multiplication and\ndivision needed to handle space on the rt volume.\n\nThe second is that (unlike in the original rtgroups design), rtgroups do\nnot have fixed-location metadata like AGs do, which means that there's\nnothing to force a break between rtgroups.\n\nTherefore, we must loop through the rtgroups in xreap_rtmeta_extent to\navoid running off the end of an rtgroup while reaping.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-19 15:17:53","updated_at":"2026-11-19 15:17:53"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/d46e7803780d5f1a7bbb889f54ab400c30508f09","name":"https://git.kernel.org/stable/c/d46e7803780d5f1a7bbb889f54ab400c30508f09","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/84c0abd7e70fde9f2f61f06287dbee82734e664a","name":"https://git.kernel.org/stable/c/84c0abd7e70fde9f2f61f06287dbee82734e664a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d7c204d4ea7ef0cf0dac908388984c2936f1f94e","name":"https://git.kernel.org/stable/c/d7c204d4ea7ef0cf0dac908388984c2936f1f94e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99412","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99412","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fd97fe1112088c16594dcd45e809f1643e623309 84c0abd7e70fde9f2f61f06287dbee82734e664a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fd97fe1112088c16594dcd45e809f1643e623309 d46e7803780d5f1a7bbb889f54ab400c30508f09 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected fd97fe1112088c16594dcd45e809f1643e623309 d7c204d4ea7ef0cf0dac908388984c2936f1f94e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.61 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.2 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/xfs/scrub/reap.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"84c0abd7e70fde9f2f61f06287dbee82734e664a","status":"affected","version":"fd97fe1112088c16594dcd45e809f1643e623309","versionType":"git"},{"lessThan":"d46e7803780d5f1a7bbb889f54ab400c30508f09","status":"affected","version":"fd97fe1112088c16594dcd45e809f1643e623309","versionType":"git"},{"lessThan":"d7c204d4ea7ef0cf0dac908388984c2936f1f94e","status":"affected","version":"fd97fe1112088c16594dcd45e809f1643e623309","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/xfs/scrub/reap.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.14"},{"lessThan":"6.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.61","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.2","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.61","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.2","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc1","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: avoid cross-rtgroup reaping after a repair\n\nLOLLM notices that the extents stored in a xrtb_bitmap (aka xfs_rtblock\nbitmap) can span multiple rtgroups due to two circumstances.  The first\nis that the size of an rtgroup is an exact power of two, which means\nthat rtgroups are adjacent in the segmented xfs_rtblock_t address space.\nThis is fairly common to reduce the amount of multiplication and\ndivision needed to handle space on the rt volume.\n\nThe second is that (unlike in the original rtgroups design), rtgroups do\nnot have fixed-location metadata like AGs do, which means that there's\nnothing to force a break between rtgroups.\n\nTherefore, we must loop through the rtgroups in xreap_rtmeta_extent to\navoid running off the end of an rtgroup while reaping."}],"providerMetadata":{"dateUpdated":"2026-11-19T14:40:08.325Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/84c0abd7e70fde9f2f61f06287dbee82734e664a"},{"url":"https://git.kernel.org/stable/c/d46e7803780d5f1a7bbb889f54ab400c30508f09"},{"url":"https://git.kernel.org/stable/c/d7c204d4ea7ef0cf0dac908388984c2936f1f94e"}],"title":"xfs: avoid cross-rtgroup reaping after a repair","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99412","datePublished":"2026-11-19T14:40:08.325Z","dateReserved":"2026-09-25T10:25:14.413Z","dateUpdated":"2026-11-19T14:40:08.325Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-19 15:17:53","lastModifiedDate":"2026-11-19 15:17:53","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99412","Ordinal":"1","Title":"xfs: avoid cross-rtgroup reaping after a repair","CVE":"CVE-2026-99412","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99412","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: avoid cross-rtgroup reaping after a repair\n\nLOLLM notices that the extents stored in a xrtb_bitmap (aka xfs_rtblock\nbitmap) can span multiple rtgroups due to two circumstances.  The first\nis that the size of an rtgroup is an exact power of two, which means\nthat rtgroups are adjacent in the segmented xfs_rtblock_t address space.\nThis is fairly common to reduce the amount of multiplication and\ndivision needed to handle space on the rt volume.\n\nThe second is that (unlike in the original rtgroups design), rtgroups do\nnot have fixed-location metadata like AGs do, which means that there's\nnothing to force a break between rtgroups.\n\nTherefore, we must loop through the rtgroups in xreap_rtmeta_extent to\navoid running off the end of an rtgroup while reaping.","Type":"Description","Title":"xfs: avoid cross-rtgroup reaping after a repair"}]}}}