Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99471

KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls

No exploitation reported by the sources we read.

  • Published2026-11-19
  • Fixed in7.3.2 · 6.18.61 · 6.12.117

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls The virtual-mode HPT hcall handlers (H_ENTER, H_REMOVE, H_BULK_REMOVE, H_CLEAR_REF, H_CLEAR_MOD) call into book3s_hv_rm_mmu.c, which accesses memslots via kvm_memslots_raw(). kvm_memslots_raw() uses rcu_dereference_raw_check() to bypass SRCU lockdep annotation checking. This is safe in real mode because the entire guest entry/exit is wrapped in srcu_read_lock/unlock inside kvmppc_run_core() and kvmhv_run_single_vcpu(). However, since commit 6165d5dd99db ("KVM: PPC: Book3S HV: add virtual mode handlers for HPT hcalls and page faults"), these same handlers are also executed in virtual mode via kvmppc_pseries_do_hcall(), which runs after SRCU has already been released on guest exit. A concurrent KVM_SET_USER_MEMORY_REGION deletion or move can therefore call synchronize_srcu_expedited() — which does not wait for this thread — and then kfree(slot) and vfree(slot->arch.rmap) while the hcall handler still holds a raw pointer to the memslot. lock_rmap() then writes to freed vmalloc memory, leading to use-after-free and memory corruption. Because kvm_memslots_raw() suppresses lockdep checks, this race is entirely silent. Fix this by factoring out the 7 HPT hcall handlers (H_REMOVE, H_ENTER, H_READ, H_CLEAR_MOD, H_CLEAR_REF, H_PROTECT, H_BULK_REMOVE) into a helper function, kvmppc_pseries_do_hpt_hcall(), and wrapping its call site in srcu_read_lock(&kvm->srcu) / srcu_read_unlock(&kvm->srcu, idx). Targeting only the HPT hcalls avoids wrapping non-HPT hcalls that sleep (such as H_CONFER, H_REGISTER_VPA, H_PAGE_INIT) or handlers that already acquire SRCU internally (such as H_RTAS).

Timeline

dates in UTC
  1. 2026-11-1914:42CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.27.3.2
6.x≥ 6.13.0, < 6.18.616.18.61
6.12≥ 5.14.0, < 6.12.1176.12.117

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d, < 0f86aba67317d65b2dc89995dd5ddefe219411a7fixed in 0f86aba67317d65b2dc89995dd5ddefe219411a7git
    • ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d, < 4ab2c987fd15a4bd28ef46a9ac871359886e6439fixed in 4ab2c987fd15a4bd28ef46a9ac871359886e6439git
    • ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d, < c3d0261c4fae2cc36dcf9f4e247552498232cafffixed in c3d0261c4fae2cc36dcf9f4e247552498232caffgit
    • ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d, < 61a39797bb136243c48b46e2586d8a9e2cea6a89fixed in 61a39797bb136243c48b46e2586d8a9e2cea6a89git
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 5.14no fix stated

    Not affected < 5.14 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-19

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • kernelAzure Linux:3all versions · no fixed version listed
  • linuxDebian:14all versions · fixed in 7.3.3-1
  • linuxDebian:13all versions · fixed in 6.12.117-1
  • linuxDebian:12all versions · no fixed version listed
  • linux-6.12Debian:12all versions · fixed in 6.12.117-1~deb12u1
  • linux-ltsAlpaquita:streamfrom 6.18.58-r0 · fixed in 6.18.62-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
  • linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed

Vendor advisories

  • CVE-2026-99471 Red Hat Product Security2 known affected

    kernel: kernel: Use-after-free in KVM PowerPC Book3S HV via virtual-mode HPT hypercalls

    kernel.src as a component of Red Hat Enterprise Linux 10 · openshift/ose-rhel-coreos-10 as a component of Red Hat OpenShift Container Platform 5

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.2 · 6.18.61 · 6.12.117
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-99471 · 2 productsAffected

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-19
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-mxfq-v49v-5g45

Frequently asked questions

What is CVE-2026-99471?

In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls The virtual-mode HPT hcall handlers (H_ENTER, H_REMOVE, H_BULK_REMOVE, H_CLEAR_REF, H_CLEAR_MOD) call into book3s_hv_rm_mmu.c, which accesses memslots via kvm_memslots_raw(). kvm_memslots_raw() uses rcu_dereference_raw_check() to bypass SRCU lockdep annotation checking. This is safe in real mode because the entire guest entry/exit is wrapped in srcu_read_lock/unlock inside kvmppc_run_core() and kvmhv_run_single_vcpu(). However, since commit 6165d5dd99db ("KVM: PPC: Book3S HV: add virtual mode handlers for HPT hcalls and page faults"), these same handlers are also executed in virtual mode via kvmppc_pseries_do_hcall(), which runs after SRCU has already been released on guest exit. A concurrent KVM_SET_USER_MEMORY_REGION deletion or move can therefore call synchronize_srcu_expedited() — which does not wait for this thread — and then kfree(slot) and vfree(slot->arch.rmap) while the hcall handler still holds a raw pointer to the memslot. lock_rmap() then writes to freed vmalloc memory, leading to use-after-free and memory corruption. Because kvm_memslots_raw() suppresses lockdep checks, this race is entirely silent. Fix this by factoring out the 7 HPT hcall handlers (H_REMOVE, H_ENTER, H_READ, H_CLEAR_MOD, H_CLEAR_REF, H_PROTECT, H_BULK_REMOVE) into a helper function, kvmppc_pseries_do_hpt_hcall(), and wrapping its call site in srcu_read_lock(&kvm->srcu) / srcu_read_unlock(&kvm->srcu, idx). Targeting only the HPT hcalls avoids wrapping non-HPT hcalls that sleep (such as H_CONFER, H_REGISTER_VPA, H_PAGE_INIT) or handlers that already acquire SRCU internally (such as H_RTAS).

Is CVE-2026-99471 actively exploited?

Active exploitation of CVE-2026-99471 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99471?

CVE-2026-99471 has a CVSS v3 base score of 7.8 (High severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record