CVE-2026-98639: Linux kernel · KVM: riscv: Fix NACL hfence entry update order
Source GCVE Database
Not known to be exploited · fixed in d6de766d8d26d71b714f548192099112def50a9c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d6de766d8d26d71b714f548192099112def50a9c, b3d346838ec65fac7fd83f5dbcedd13cadfffddb, 6da466502621381fa88a6684290923d25c559266
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to d6de766d8d26d71b714f548192099112def50a9c, b3d346838ec65fac7fd83f5dbcedd13cadfffddb or 6da466502621381fa88a6684290923d25c559266.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to correct the update order of the nested HFENCE entry in the KVM RISC-V code. Users should update to a Linux kernel version that includes this fix. Since no specific patch links or versions are provided, check the vendor or kernel release notes for the official fix. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel's KVM implementation for RISC-V was resolved by correcting the order of updates to the nested HFENCE (hfence) entry. The issue involved writing the Config word before updating the Page_Number and Page_Count, which could cause incorrect TLB flush ranges due to stale values being observed. The fix ensures the page number and count are written first, followed by the Config word, using memory barriers to prevent reordering.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98639 (opens in a new tab)
- git.kernel.org/stable/c/6da466502621381fa88a6684290923d25c559266 (opens in a new tab)
- git.kernel.org/stable/c/b3d346838ec65fac7fd83f5dbcedd13cadfffddb (opens in a new tab)
- git.kernel.org/stable/c/d6de766d8d26d71b714f548192099112def50a9c (opens in a new tab)