GHSA-3XCR-F59C-PJVQ
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In the Linux kernel, the following vulnerability has been resolved:
btrfs: unlock inode and extent in caller when io_uring read extent fails
btrfs_uring_read_extent() runs only after btrfs_encoded_read() has taken the inode shared lock and the extent lock. On failure it used to unlock in out_fail, and a pages-array allocation failure returned -ENOMEM without unlocking at all.
Unlock in the caller instead on all failure returns, matching the copy_to_user() error path. The deferred -EIOCBQUEUED path still unlocks in btrfs_uring_read_finished().
{
"affected": [],
"aliases": [
"CVE-2026-98961"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:17Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: unlock inode and extent in caller when io_uring read extent fails\n\nbtrfs_uring_read_extent() runs only after btrfs_encoded_read() has taken\nthe inode shared lock and the extent lock. On failure it used to unlock\nin out_fail, and a pages-array allocation failure returned -ENOMEM\nwithout unlocking at all.\n\nUnlock in the caller instead on all failure returns, matching the\ncopy_to_user() error path. The deferred -EIOCBQUEUED path still unlocks\nin btrfs_uring_read_finished().",
"id": "GHSA-3xcr-f59c-pjvq",
"modified": "2026-10-23T15:31:32Z",
"published": "2026-10-23T15:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98961"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2797eb38773a96914ccedeec71eb2144645400b2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ada1fc725a4db407294ae90a0d40ef1c46f457f2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b6e8add5d79d1f6f819a054c833bab452bd7365d"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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
Loading timeline…
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.