GHSA-28MC-JVX2-G85V
Vulnerability from github – Published: 2025-02-10 18:30 – Updated: 2025-02-10 18:30In the Linux kernel, the following vulnerability has been resolved:
io_uring/rsrc: require cloned buffers to share accounting contexts
When IORING_REGISTER_CLONE_BUFFERS is used to clone buffers from uring instance A to uring instance B, where A and B use different MMs for accounting, the accounting can go wrong: If uring instance A is closed before uring instance B, the pinned memory counters for uring instance B will be decremented, even though the pinned memory was originally accounted through uring instance A; so the MM of uring instance B can end up with negative locked memory.
{
"affected": [],
"aliases": [
"CVE-2025-21686"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-10T16:15:38Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/rsrc: require cloned buffers to share accounting contexts\n\nWhen IORING_REGISTER_CLONE_BUFFERS is used to clone buffers from uring\ninstance A to uring instance B, where A and B use different MMs for\naccounting, the accounting can go wrong:\nIf uring instance A is closed before uring instance B, the pinned memory\ncounters for uring instance B will be decremented, even though the pinned\nmemory was originally accounted through uring instance A; so the MM of\nuring instance B can end up with negative locked memory.",
"id": "GHSA-28mc-jvx2-g85v",
"modified": "2025-02-10T18:30:47Z",
"published": "2025-02-10T18:30:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-21686"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/19d340a2988d4f3e673cded9dde405d727d7e248"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cafc60ae35f82ebf156b3245f979ca61cbb8e42c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/efd96fbe23fa87de39116f632401f67b93be21ab"
}
],
"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.