GHSA-C5CF-C6GM-HV9C
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix valid block count leak on data block allocation failure
In __allocate_data_block(), when allocating a new data block (dn->data_blkaddr == NULL_ADDR), inc_valid_block_count() is called first to increment total_valid_block_count and i_blocks. If the subsequent f2fs_allocate_data_block() fails, the function returns the error directly without rolling back the already-incremented block counts, causing a permanent leak.
Fix this by calling dec_valid_block_count() to undo the increment before returning the error. The condition old_blkaddr == NULL_ADDR precisely identifies the case where inc_valid_block_count() was called.
{
"affected": [],
"aliases": [
"CVE-2026-89830"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:49Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix valid block count leak on data block allocation failure\n\nIn __allocate_data_block(), when allocating a new data block\n(dn-\u003edata_blkaddr == NULL_ADDR), inc_valid_block_count() is\ncalled first to increment total_valid_block_count and i_blocks.\nIf the subsequent f2fs_allocate_data_block() fails, the function\nreturns the error directly without rolling back the\nalready-incremented block counts, causing a permanent leak.\n\nFix this by calling dec_valid_block_count() to undo the\nincrement before returning the error. The condition\nold_blkaddr == NULL_ADDR precisely identifies the case where\ninc_valid_block_count() was called.",
"id": "GHSA-c5cf-c6gm-hv9c",
"modified": "2026-09-16T12:30:38Z",
"published": "2026-09-16T12:30:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89830"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0f9af07ecc1ab486038373db6ae0436c5d674b19"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2d50b6d47e5671ff6a25834c5906d443356191f0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/931e1aa4d44c52ff8e0feb38420a8827c62e886b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dde99df5a9d3b0ca6ac0a86f98799685f7399432"
}
],
"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.