CVE-2026-99412 (GCVE-0-2026-99412)

Vulnerability from cvelistv5 – Published: 2026-11-19 14:40 – Updated: 2026-11-19 14:40
VLAI
Title
xfs: avoid cross-rtgroup reaping after a repair
Summary
In the Linux kernel, the following vulnerability has been resolved: xfs: avoid cross-rtgroup reaping after a repair LOLLM notices that the extents stored in a xrtb_bitmap (aka xfs_rtblock bitmap) can span multiple rtgroups due to two circumstances. The first is that the size of an rtgroup is an exact power of two, which means that rtgroups are adjacent in the segmented xfs_rtblock_t address space. This is fairly common to reduce the amount of multiplication and division needed to handle space on the rt volume. The second is that (unlike in the original rtgroups design), rtgroups do not have fixed-location metadata like AGs do, which means that there's nothing to force a break between rtgroups. Therefore, we must loop through the rtgroups in xreap_rtmeta_extent to avoid running off the end of an rtgroup while reaping.
Severity
No CVSS data available.
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 7143 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: fd97fe1112088c16594dcd45e809f1643e623309 , < 84c0abd7e70fde9f2f61f06287dbee82734e664a (git)
Affected: fd97fe1112088c16594dcd45e809f1643e623309 , < d46e7803780d5f1a7bbb889f54ab400c30508f09 (git)
Affected: fd97fe1112088c16594dcd45e809f1643e623309 , < d7c204d4ea7ef0cf0dac908388984c2936f1f94e (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.14
Unaffected: 0 , < 6.14 (semver)
Unaffected: 6.18.61 , ≤ 6.18.* (semver)
Unaffected: 7.3.2 , ≤ 7.3.* (semver)
Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "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\u0027s\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",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-99412",
      "date": "2026-11-20",
      "epss": "0.00155",
      "percentile": "0.04708"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "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"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "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\u0027s\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."
          }
        ],
        "id": "CVE-2026-99412",
        "lastModified": "2026-11-19T15:17:53.877",
        "metrics": {},
        "published": "2026-11-19T15:17:53.877",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/84c0abd7e70fde9f2f61f06287dbee82734e664a"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/d46e7803780d5f1a7bbb889f54ab400c30508f09"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/d7c204d4ea7ef0cf0dac908388984c2936f1f94e"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-19T21:50:45+00:00",
      "cve": "CVE-2026-99412",
      "id": "CVE-2026-99412",
      "initial_release_date": "2026-11-19T14:40:08.325000+00:00",
      "product_status:known_affected": "2",
      "product_status:known_not_affected": "202",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: kernel: Denial of service via out-of-bounds access in XFS repair",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99412.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.