FKIE_CVE-2026-99471

Vulnerability from fkie_nvd - Published: 2026-11-19 15:18 - Updated: 2026-11-19 15:18
Severity
Summary
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).
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/powerpc/kvm/book3s_hv.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "0f86aba67317d65b2dc89995dd5ddefe219411a7",
              "status": "affected",
              "version": "6165d5dd99dbaec7a309491c3951bd81fc89978d",
              "versionType": "git"
            },
            {
              "lessThan": "4ab2c987fd15a4bd28ef46a9ac871359886e6439",
              "status": "affected",
              "version": "6165d5dd99dbaec7a309491c3951bd81fc89978d",
              "versionType": "git"
            },
            {
              "lessThan": "c3d0261c4fae2cc36dcf9f4e247552498232caff",
              "status": "affected",
              "version": "6165d5dd99dbaec7a309491c3951bd81fc89978d",
              "versionType": "git"
            },
            {
              "lessThan": "61a39797bb136243c48b46e2586d8a9e2cea6a89",
              "status": "affected",
              "version": "6165d5dd99dbaec7a309491c3951bd81fc89978d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/powerpc/kvm/book3s_hv.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.14"
            },
            {
              "lessThan": "5.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.117",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.61",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: PPC: Book3S HV: Add SRCU protection for virtual-mode HPT hcalls\n\nThe virtual-mode HPT hcall handlers (H_ENTER, H_REMOVE, H_BULK_REMOVE,\nH_CLEAR_REF, H_CLEAR_MOD) call into book3s_hv_rm_mmu.c, which accesses\nmemslots via kvm_memslots_raw().  kvm_memslots_raw() uses\nrcu_dereference_raw_check() to bypass SRCU lockdep annotation checking.\nThis is safe in real mode because the entire guest entry/exit is wrapped\nin srcu_read_lock/unlock inside kvmppc_run_core() and\nkvmhv_run_single_vcpu().\n\nHowever, since commit 6165d5dd99db (\"KVM: PPC: Book3S HV: add virtual\nmode handlers for HPT hcalls and page faults\"), these same handlers are\nalso executed in virtual mode via kvmppc_pseries_do_hcall(), which runs\nafter SRCU has already been released on guest exit.\n\nA concurrent KVM_SET_USER_MEMORY_REGION deletion or move can therefore\ncall synchronize_srcu_expedited() \u2014 which does not wait for this thread \u2014\nand then kfree(slot) and vfree(slot-\u003earch.rmap) while the hcall handler\nstill holds a raw pointer to the memslot.  lock_rmap() then writes to\nfreed vmalloc memory, leading to use-after-free and memory corruption.\nBecause kvm_memslots_raw() suppresses lockdep checks, this race is\nentirely silent.\n\nFix this by factoring out the 7 HPT hcall handlers (H_REMOVE, H_ENTER,\nH_READ, H_CLEAR_MOD, H_CLEAR_REF, H_PROTECT, H_BULK_REMOVE) into a\nhelper function, kvmppc_pseries_do_hpt_hcall(), and wrapping its call\nsite in srcu_read_lock(\u0026kvm-\u003esrcu) / srcu_read_unlock(\u0026kvm-\u003esrcu, idx).\nTargeting only the HPT hcalls avoids wrapping non-HPT hcalls that sleep\n(such as H_CONFER, H_REGISTER_VPA, H_PAGE_INIT) or handlers that already\nacquire SRCU internally (such as H_RTAS)."
    }
  ],
  "id": "CVE-2026-99471",
  "lastModified": "2026-11-19T15:18:01.503",
  "metrics": {},
  "published": "2026-11-19T15:18:01.503",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/0f86aba67317d65b2dc89995dd5ddefe219411a7"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/4ab2c987fd15a4bd28ef46a9ac871359886e6439"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/61a39797bb136243c48b46e2586d8a9e2cea6a89"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/c3d0261c4fae2cc36dcf9f4e247552498232caff"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.