Answer in brief
CVE-2026-64592 records a Unknown severity vulnerability in riscv: mm: Unconditionally sfence.vma for spurious fault. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=503638e0babf364061bc50fca5103b00a56cc50a <c4df24702bfc3cd2bed7746b94dc6139a3fa5428 || >=503638e0babf364061bc50fca5103b00a56cc50a <4d730cab96e6b75e4a07c4baf37294ebc07f795e || >=503638e0babf364061bc50fca5103b00a56cc50a <ede985ff4b569ed2454024f8bb107a6729fe08aa || >=503638e0babf364061bc50fca5103b00a56cc50a <1b2c6b56a9fa0dcbef461039937de22b1cbecc7d | c4df24702bfc3cd2bed7746b94dc6139a3fa5428, 4d730cab96e6b75e4a07c4baf37294ebc07f795e, ede985ff4b569ed2454024f8bb107a6729fe08aa, 1b2c6b56a9fa0dcbef461039937de22b1cbecc7d |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
In 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64592 records a Unknown severity vulnerability in riscv: mm: Unconditionally sfence.vma for spurious fault. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=503638e0babf364061bc50fca5103b00a56cc50a <c4df24702bfc3cd2bed7746b94dc6139a3fa5428 || >=503638e0babf364061bc50fca5103b00a56cc50a <4d730cab96e6b75e4a07c4baf37294ebc07f795e || >=503638e0babf364061bc50fca5103b00a56cc50a <ede985ff4b569ed2454024f8bb107a6729fe08aa || >=503638e0babf364061bc50fca5103b00a56cc50a <1b2c6b56a9fa0dcbef461039937de22b1cbecc7d | c4df24702bfc3cd2bed7746b94dc6139a3fa5428, 4d730cab96e6b75e4a07c4baf37294ebc07f795e, ede985ff4b569ed2454024f8bb107a6729fe08aa, 1b2c6b56a9fa0dcbef461039937de22b1cbecc7d |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
In 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.
Quoted source text, attributed separately from HOL analysis.