Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48727

KVM: arm64: Avoid consuming a stale esr value when SError occur

High7.3EPSS 0.22%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Avoid consuming a stale esr value when SError occur When any exception other than an IRQ occurs, the CPU updates the ESR_EL2 register with the exception syndrome. An SError may also become pending, and will be synchronised by KVM. KVM notes the exception type, and whether an SError was synchronised in exit_code. When an exception other than an IRQ occurs, fixup_guest_exit() updates vcpu->arch.fault.esr_el2 from the hardware register. When an SError was synchronised, the vcpu esr value is used to determine if the exception was due to an HVC. If so, ELR_EL2 is moved back one instruction. This is so that KVM can process the SError first, and re-execute the HVC if the guest survives the SError. But if an IRQ synchronises an SError, the vcpu's esr value is stale. If the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2, causing an unrelated guest instruction to be executed twice. Check ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don't update this register so don't need to check.

Scores

CVSS scores of CVE-2022-48727, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected defe21f49bc98b095300752aa1e19bb608f3e97d – < e1e852746997500f1873f60b954da5f02cc2dba3
    • affected defe21f49bc98b095300752aa1e19bb608f3e97d – < 57e2986c3b25092691a6e3d6ee9168caf8978932
    • affected defe21f49bc98b095300752aa1e19bb608f3e97d – < 1c71dbc8a179d99dd9bb7e7fc1888db613cf85de
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.22 – ≤ 5.15.*
    • unaffected 5.16.8 – ≤ 5.16.*
    • unaffected 5.17 – ≤ *

References (3)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48727 badge
[![CVE-2022-48727](https://trackcve.app/badge/CVE-2022-48727.svg)](https://trackcve.app/cve/CVE-2022-48727)

Record last updated .