# CVE-2026-99471: KVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls

Status: published. Published: 2026-11-19. Updated: 2026-11-22.

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).

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d; < 0f86aba67317d65b2dc89995dd5ddefe219411a7 (affected, git); ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d; < 4ab2c987fd15a4bd28ef46a9ac871359886e6439 (affected, git); ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d; < c3d0261c4fae2cc36dcf9f4e247552498232caff (affected, git); ≥ 6165d5dd99dbaec7a309491c3951bd81fc89978d; < 61a39797bb136243c48b46e2586d8a9e2cea6a89 (affected, git). Source: CNA: Linux
- Linux / Linux: 5.14 (affected); ≥ 0; < 5.14 (unaffected, semver); ≥ 6.12.117; ≤ 6.12.* (unaffected, semver); ≥ 6.18.61; ≤ 6.18.* (unaffected, semver); ≥ 7.3.2; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.18% as of 2026-11-21; percentile 7.31%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/0f86aba67317d65b2dc89995dd5ddefe219411a7 (CNA: Linux)

- https://git.kernel.org/stable/c/4ab2c987fd15a4bd28ef46a9ac871359886e6439 (CNA: Linux)

- https://git.kernel.org/stable/c/c3d0261c4fae2cc36dcf9f4e247552498232caff (CNA: Linux)

- https://git.kernel.org/stable/c/61a39797bb136243c48b46e2586d8a9e2cea6a89 (CNA: Linux)

- https://git.kernel.org/stable/c/0f86aba67317d65b2dc89995dd5ddefe219411a7 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/4ab2c987fd15a4bd28ef46a9ac871359886e6439 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/61a39797bb136243c48b46e2586d8a9e2cea6a89 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/c3d0261c4fae2cc36dcf9f4e247552498232caff (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99471; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99471; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99471; retrieved 2026-11-22; source updated Not reported

Revision: 161d304a5d397f4d8805e412b5705d2c05707cb8aba43a8fd8375cbc2423efa6

Canonical: https://y2.dev/cve/CVE-2026-99471

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.