GHSA-8R8R-JGJJ-W55R
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
xfs: don't let hidden_space go negative in xfs_metafile_resv_init
LOLLM points out that if the amount of fdblocks that we can reserve for a metadata btree file goes below the space already used by that file, then the hidden_space subtraction can underflow, causing xfs_dec_fdblocks to subtract a huge amount of space. We never want the target to be less than the used sapce, so fix the logic that adjusts dblocks_avail downwards.
Also fix an error in the adjacent comment.
{
"affected": [],
"aliases": [
"CVE-2026-98446"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:16:54Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: don\u0027t let hidden_space go negative in xfs_metafile_resv_init\n\nLOLLM points out that if the amount of fdblocks that we can reserve for\na metadata btree file goes below the space already used by that file,\nthen the hidden_space subtraction can underflow, causing\nxfs_dec_fdblocks to subtract a huge amount of space. We never want the\ntarget to be less than the used sapce, so fix the logic that adjusts\ndblocks_avail downwards.\n\nAlso fix an error in the adjacent comment.",
"id": "GHSA-8r8r-jgjj-w55r",
"modified": "2026-10-18T18:31:49Z",
"published": "2026-10-18T18:31:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98446"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/476582d754cdc5110f806001417fea6c77824c13"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/930a9c1c321efdaa3e7f8caecb0479cee3baf342"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f0d8352a39f4a2e329ae45b71bb0d49e2ca0a6dc"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.