GHSA-M6HV-9H66-MMJV
Vulnerability from github – Published: 2026-08-06 09:30 – Updated: 2026-08-06 09:30In the Linux kernel, the following vulnerability has been resolved:
riscv: mm: Unconditionally sfence.vma for spurious fault
Svvptc does not guarantee that it's safe to just return here. Since we have already cleared our bit, if, theoretically, the bounded timeframe for the accessed page to become valid still hasn't happened after sret, we could fault again and actually crash.
Hopefully, these spurious faults should be rare enough that this is an acceptable slowdown.
{
"affected": [],
"aliases": [
"CVE-2026-64592"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-06T08:16:34Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: mm: Unconditionally sfence.vma for spurious fault\n\nSvvptc does not guarantee that it\u0027s safe to just return here. Since we\nhave already cleared our bit, if, theoretically, the bounded timeframe\nfor the accessed page to become valid still hasn\u0027t happened after sret,\nwe could fault again and actually crash.\n\nHopefully, these spurious faults should be rare enough that this is an\nacceptable slowdown.",
"id": "GHSA-m6hv-9h66-mmjv",
"modified": "2026-08-06T09:30:33Z",
"published": "2026-08-06T09:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64592"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1b2c6b56a9fa0dcbef461039937de22b1cbecc7d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4d730cab96e6b75e4a07c4baf37294ebc07f795e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c4df24702bfc3cd2bed7746b94dc6139a3fa5428"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ede985ff4b569ed2454024f8bb107a6729fe08aa"
}
],
"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.