KVM: riscv: Fix NACL hfence entry update order
Summary
| CVE | CVE-2026-98639 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:17 UTC |
| Updated | 2026-10-19 10:19:28 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
KVM: riscv: Fix NACL hfence entry update order
The SBI v3.0 specification (section 15.1.2) requires a nested HFENCE
entry to be populated as follows:
1) find an unused entry with Config.Pending == 0
2) update the Page_Number and Page_Count words
3) update the Config word with Config.Pending set
__kvm_riscv_nacl_hfence() writes the Config word first, so the SBI
implementation (or NACL hardware) can observe a pending entry with
pnum/pcount values left over from the previous use of that entry,
resulting in incorrect TLB flush ranges.
Write pnum and pcount first and the Config word last. Since the
consumer is an external agent on coherent shared memory, use
WRITE_ONCE() to stop the compiler from reordering the stores and
smp_wmb() to make the parameter words globally visible before the
Pending bit is set. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected d466c19cead5904d4d5d92adb2b213b411d3b849 d6de766d8d26d71b714f548192099112def50a9c git |
Not specified |
| CNA |
Linux |
Linux |
affected d466c19cead5904d4d5d92adb2b213b411d3b849 6da466502621381fa88a6684290923d25c559266 git |
Not specified |
| CNA |
Linux |
Linux |
affected d466c19cead5904d4d5d92adb2b213b411d3b849 b3d346838ec65fac7fd83f5dbcedd13cadfffddb git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.13 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.13 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.55 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.9 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/6da466502621381fa88a6684290923d25c559266 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b3d346838ec65fac7fd83f5dbcedd13cadfffddb |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d6de766d8d26d71b714f548192099112def50a9c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.