GHSA-HXMF-49Q3-QMV4
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
btrfs: retry verity reads for not-uptodate Merkle folios
btrfs_read_merkle_tree_page() can find a folio in the mapping that is not uptodate. After taking the folio lock, the current code treats that state as a read error and returns -EIO.
That can make a previous transient read failure sticky. If the failed read left a not-uptodate folio in the mapping, later callers find that folio and fail instead of retrying the read.
Keep the existing page-cache insertion and locking order, but retry the Merkle item read when a not-uptodate folio is found in the mapping. Also unlock the folio when read_key_bytes() fails so that a later caller can lock it and retry the read.
{
"affected": [],
"aliases": [
"CVE-2026-90262"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:22Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: retry verity reads for not-uptodate Merkle folios\n\nbtrfs_read_merkle_tree_page() can find a folio in the mapping that is not\nuptodate. After taking the folio lock, the current code treats that state\nas a read error and returns -EIO.\n\nThat can make a previous transient read failure sticky. If the failed read\nleft a not-uptodate folio in the mapping, later callers find that folio and\nfail instead of retrying the read.\n\nKeep the existing page-cache insertion and locking order, but retry the\nMerkle item read when a not-uptodate folio is found in the mapping. Also\nunlock the folio when read_key_bytes() fails so that a later caller can\nlock it and retry the read.",
"id": "GHSA-hxmf-49q3-qmv4",
"modified": "2026-09-17T18:31:58Z",
"published": "2026-09-17T18:31:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90262"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/12b6d1a1715cbced2e445ca353f9c9987b8636e2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/81241f734f0f662378f5ffc53882b012923e6fe5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8cc569696dac51fc62bb39b3b8f530582b916d29"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/90e9eae1b5907fa36620ffb7f4f1a4afa9333427"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c1fa005cdf3b7ff14cdfd7d512830088a3fc256b"
}
],
"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.