CVE-2022-48727 (GCVE-0-2022-48727)

Vulnerability from cvelistv5 – Published: 2024-06-20 11:13 – Updated: 2026-08-05 08:51
VLAI
Title
KVM: arm64: Avoid consuming a stale esr value when SError occur
Summary
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.
Severity
7.3 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: defe21f49bc98b095300752aa1e19bb608f3e97d , < e1e852746997500f1873f60b954da5f02cc2dba3 (git)
Affected: defe21f49bc98b095300752aa1e19bb608f3e97d , < 57e2986c3b25092691a6e3d6ee9168caf8978932 (git)
Affected: defe21f49bc98b095300752aa1e19bb608f3e97d , < 1c71dbc8a179d99dd9bb7e7fc1888db613cf85de (git)
Create a notification for this product.
Linux Linux Affected: 5.11
Unaffected: 0 , < 5.11 (semver)
Unaffected: 5.15.22 , ≤ 5.15.* (semver)
Unaffected: 5.16.8 , ≤ 5.16.* (semver)
Unaffected: 5.17 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2022-48727",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-06-20T16:20:44.710184Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-20T16:20:53.835Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T15:24:59.975Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/arm64/kvm/hyp/include/hyp/switch.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "e1e852746997500f1873f60b954da5f02cc2dba3",
              "status": "affected",
              "version": "defe21f49bc98b095300752aa1e19bb608f3e97d",
              "versionType": "git"
            },
            {
              "lessThan": "57e2986c3b25092691a6e3d6ee9168caf8978932",
              "status": "affected",
              "version": "defe21f49bc98b095300752aa1e19bb608f3e97d",
              "versionType": "git"
            },
            {
              "lessThan": "1c71dbc8a179d99dd9bb7e7fc1888db613cf85de",
              "status": "affected",
              "version": "defe21f49bc98b095300752aa1e19bb608f3e97d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/arm64/kvm/hyp/include/hyp/switch.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.11"
            },
            {
              "lessThan": "5.11",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.22",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.16.*",
              "status": "unaffected",
              "version": "5.16.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "5.17",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.22",
                  "versionStartIncluding": "5.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.16.8",
                  "versionStartIncluding": "5.11",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.17",
                  "versionStartIncluding": "5.11",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Avoid consuming a stale esr value when SError occur\n\nWhen any exception other than an IRQ occurs, the CPU updates the ESR_EL2\nregister with the exception syndrome. An SError may also become pending,\nand will be synchronised by KVM. KVM notes the exception type, and whether\nan SError was synchronised in exit_code.\n\nWhen an exception other than an IRQ occurs, fixup_guest_exit() updates\nvcpu-\u003earch.fault.esr_el2 from the hardware register. When an SError was\nsynchronised, the vcpu esr value is used to determine if the exception\nwas due to an HVC. If so, ELR_EL2 is moved back one instruction. This\nis so that KVM can process the SError first, and re-execute the HVC if\nthe guest survives the SError.\n\nBut if an IRQ synchronises an SError, the vcpu\u0027s esr value is stale.\nIf the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2,\ncausing an unrelated guest instruction to be executed twice.\n\nCheck ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don\u0027t\nupdate this register so don\u0027t need to check."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.3,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The bug is in KVM arm64 hyp `fixup_guest_exit()` during a guest exit; it is reached only by running an arm64 KVM guest (or locally via /dev/kvm), not by network packet processing or physical device attachment.\nAC:L - A guest can poison `vcpu-\u003earch.fault.esr_el2` with HVC, IRQs occur routinely, and on worst-case arm64 deployments (assigned devices/RAS) the guest can induce a pending SError that is synchronized on IRQ exit\u2014no attacker-uncontrollable lottery beyond that.\nPR:L - Triggering needs only the ability to run guest code under KVM; /dev/kvm is typically reachable by an unprivileged kvm-group user, and a cloud/Android tenant guest needs no host CAP_SYS_ADMIN.\nUI:N - The attacker drives guest HVC activity and the SError/IRQ exit path themselves; no separate victim action such as mounting a filesystem is required.\nS:C - The defect is in the host hypervisor, but the corrupted resource is guest ELR/PC saved into `ctxt-\u003eregs.pc`, so impact lands in the guest OS\u2014a distinct security authority (same pattern as CVE-2025-21839).\nC:N - The bug only subtracts 4 from guest ELR when a stale ESR looks like HVC; it does not disclose host or cross-VM memory and provides no read primitive.\nI:L - KVM corrupts guest control flow by re-executing one unrelated instruction (PC-=4), which can alter guest state, but the modification is confined to that single rollback and is not an arbitrary write or host memory corruption.\nA:H - Resuming the guest at the wrong PC after SError handling can crash, hang, or permanently mis-execute the guest workload, fully denying availability of that VM."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T08:51:59.189Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3"
        },
        {
          "url": "https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932"
        },
        {
          "url": "https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de"
        }
      ],
      "title": "KVM: arm64: Avoid consuming a stale esr value when SError occur",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-48727",
    "datePublished": "2024-06-20T11:13:16.668Z",
    "dateReserved": "2024-06-20T11:09:39.052Z",
    "dateUpdated": "2026-08-05T08:51:59.189Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2022-48727",
      "date": "2026-08-09",
      "epss": "0.00225",
      "percentile": "0.13173"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: arm64: Avoid consuming a stale esr value when SError occur\\n\\nWhen any exception other than an IRQ occurs, the CPU updates the ESR_EL2\\nregister with the exception syndrome. An SError may also become pending,\\nand will be synchronised by KVM. KVM notes the exception type, and whether\\nan SError was synchronised in exit_code.\\n\\nWhen an exception other than an IRQ occurs, fixup_guest_exit() updates\\nvcpu-\u003earch.fault.esr_el2 from the hardware register. When an SError was\\nsynchronised, the vcpu esr value is used to determine if the exception\\nwas due to an HVC. If so, ELR_EL2 is moved back one instruction. This\\nis so that KVM can process the SError first, and re-execute the HVC if\\nthe guest survives the SError.\\n\\nBut if an IRQ synchronises an SError, the vcpu\u0027s esr value is stale.\\nIf the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2,\\ncausing an unrelated guest instruction to be executed twice.\\n\\nCheck ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don\u0027t\\nupdate this register so don\u0027t need to check.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se resolvi\\u00f3 la siguiente vulnerabilidad: KVM: arm64: Evite consumir un valor esr obsoleto cuando ocurre un SError Cuando ocurre cualquier excepci\\u00f3n que no sea una IRQ, la CPU actualiza el registro ESR_EL2 con el s\\u00edndrome de excepci\\u00f3n. Un SError tambi\\u00e9n puede quedar pendiente y KVM lo sincronizar\\u00e1. KVM anota el tipo de excepci\\u00f3n y si se sincroniz\\u00f3 un SError en exit_code. Cuando ocurre una excepci\\u00f3n distinta a una IRQ, fixup_guest_exit() actualiza vcpu-\u0026gt;arch.fault.esr_el2 desde el registro de hardware. Cuando se sincroniza un SError, el valor de vcpu esr se utiliza para determinar si la excepci\\u00f3n se debi\\u00f3 a un HVC. Si es as\\u00ed, ELR_EL2 retrocede una instrucci\\u00f3n. Esto es para que KVM pueda procesar el SError primero y volver a ejecutar el HVC si el invitado sobrevive al SError. Pero si una IRQ sincroniza un SError, el valor esr de la vcpu est\\u00e1 obsoleto. Si la excepci\\u00f3n anterior no IRQ era un HVC, KVM da\\u00f1ar\\u00e1 ELR_EL2, lo que provocar\\u00e1 que se ejecute dos veces una instrucci\\u00f3n invitada no relacionada. Verifique ARM_EXCEPTION_CODE() antes de jugar con ELR_EL2, las IRQ no actualizan este registro, por lo que no es necesario verificarlo.\"}]",
      "id": "CVE-2022-48727",
      "lastModified": "2024-11-21T07:33:52.460",
      "published": "2024-06-20T12:15:11.167",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-48727\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-06-20T12:15:11.167\",\"lastModified\":\"2026-08-04T10:17:17.970\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: arm64: Avoid consuming a stale esr value when SError occur\\n\\nWhen any exception other than an IRQ occurs, the CPU updates the ESR_EL2\\nregister with the exception syndrome. An SError may also become pending,\\nand will be synchronised by KVM. KVM notes the exception type, and whether\\nan SError was synchronised in exit_code.\\n\\nWhen an exception other than an IRQ occurs, fixup_guest_exit() updates\\nvcpu-\u003earch.fault.esr_el2 from the hardware register. When an SError was\\nsynchronised, the vcpu esr value is used to determine if the exception\\nwas due to an HVC. If so, ELR_EL2 is moved back one instruction. This\\nis so that KVM can process the SError first, and re-execute the HVC if\\nthe guest survives the SError.\\n\\nBut if an IRQ synchronises an SError, the vcpu\u0027s esr value is stale.\\nIf the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2,\\ncausing an unrelated guest instruction to be executed twice.\\n\\nCheck ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don\u0027t\\nupdate this register so don\u0027t need to check.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: KVM: arm64: Evite consumir un valor esr obsoleto cuando ocurre un SError Cuando ocurre cualquier excepci\u00f3n que no sea una IRQ, la CPU actualiza el registro ESR_EL2 con el s\u00edndrome de excepci\u00f3n. Un SError tambi\u00e9n puede quedar pendiente y KVM lo sincronizar\u00e1. KVM anota el tipo de excepci\u00f3n y si se sincroniz\u00f3 un SError en exit_code. Cuando ocurre una excepci\u00f3n distinta a una IRQ, fixup_guest_exit() actualiza vcpu-\u0026gt;arch.fault.esr_el2 desde el registro de hardware. Cuando se sincroniza un SError, el valor de vcpu esr se utiliza para determinar si la excepci\u00f3n se debi\u00f3 a un HVC. Si es as\u00ed, ELR_EL2 retrocede una instrucci\u00f3n. Esto es para que KVM pueda procesar el SError primero y volver a ejecutar el HVC si el invitado sobrevive al SError. Pero si una IRQ sincroniza un SError, el valor esr de la vcpu est\u00e1 obsoleto. Si la excepci\u00f3n anterior no IRQ era un HVC, KVM da\u00f1ar\u00e1 ELR_EL2, lo que provocar\u00e1 que se ejecute dos veces una instrucci\u00f3n invitada no relacionada. Verifique ARM_EXCEPTION_CODE() antes de jugar con ELR_EL2, las IRQ no actualizan este registro, por lo que no es necesario verificarlo.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"arch/arm64/kvm/hyp/include/hyp/switch.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"defe21f49bc98b095300752aa1e19bb608f3e97d\",\"lessThan\":\"e1e852746997500f1873f60b954da5f02cc2dba3\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"defe21f49bc98b095300752aa1e19bb608f3e97d\",\"lessThan\":\"57e2986c3b25092691a6e3d6ee9168caf8978932\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"defe21f49bc98b095300752aa1e19bb608f3e97d\",\"lessThan\":\"1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"arch/arm64/kvm/hyp/include/hyp/switch.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.11\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.11\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.22\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.16.8\",\"lessThanOrEqual\":\"5.16.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.17\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H\",\"baseScore\":7.3,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.0,\"impactScore\":4.7},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2024-06-20T16:20:44.710184Z\",\"id\":\"CVE-2022-48727\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.11\",\"versionEndExcluding\":\"5.15.22\",\"matchCriteriaId\":\"74528AA6-B524-4C3F-B188-1194235FE47D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"5.16.8\",\"matchCriteriaId\":\"0623892A-E3E4-44E6-8A5E-39A0B47AF782\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"7BD5F8D9-54FA-4CB0-B4F0-CB0471FDDB2D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.17:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"E6E34B23-78B4-4516-9BD8-61B33F4AC49A\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-08-04T23:00:38+00:00",
      "cve": "CVE-2022-48727",
      "id": "CVE-2022-48727",
      "initial_release_date": "2022-01-01T00:00:00+00:00",
      "product_status:known_affected": "108",
      "product_status:known_not_affected": "90",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: KVM: arm64: Avoid consuming a stale esr value when SError occur",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-48727.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-07T00:23:32Z",
      "cve": "CVE-2022-48727",
      "id": "CVE-2022-48727",
      "initial_release_date": "2024-06-22T04:09:24Z",
      "product_status:known_affected": "330",
      "product_status:known_not_affected": "205",
      "product_status:recommended": "391",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2022-48727",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2022-48727.json",
      "version": "54"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-03T15:24:59.975Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-48727\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-06-20T16:20:44.710184Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-06-20T16:20:50.325Z\"}}], \"cna\": {\"title\": \"KVM: arm64: Avoid consuming a stale esr value when SError occur\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.3, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The bug is in KVM arm64 hyp `fixup_guest_exit()` during a guest exit; it is reached only by running an arm64 KVM guest (or locally via /dev/kvm), not by network packet processing or physical device attachment.\\nAC:L - A guest can poison `vcpu-\u003earch.fault.esr_el2` with HVC, IRQs occur routinely, and on worst-case arm64 deployments (assigned devices/RAS) the guest can induce a pending SError that is synchronized on IRQ exit\\u2014no attacker-uncontrollable lottery beyond that.\\nPR:L - Triggering needs only the ability to run guest code under KVM; /dev/kvm is typically reachable by an unprivileged kvm-group user, and a cloud/Android tenant guest needs no host CAP_SYS_ADMIN.\\nUI:N - The attacker drives guest HVC activity and the SError/IRQ exit path themselves; no separate victim action such as mounting a filesystem is required.\\nS:C - The defect is in the host hypervisor, but the corrupted resource is guest ELR/PC saved into `ctxt-\u003eregs.pc`, so impact lands in the guest OS\\u2014a distinct security authority (same pattern as CVE-2025-21839).\\nC:N - The bug only subtracts 4 from guest ELR when a stale ESR looks like HVC; it does not disclose host or cross-VM memory and provides no read primitive.\\nI:L - KVM corrupts guest control flow by re-executing one unrelated instruction (PC-=4), which can alter guest state, but the modification is confined to that single rollback and is not an arbitrary write or host memory corruption.\\nA:H - Resuming the guest at the wrong PC after SError handling can crash, hang, or permanently mis-execute the guest workload, fully denying availability of that VM.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"defe21f49bc98b095300752aa1e19bb608f3e97d\", \"lessThan\": \"e1e852746997500f1873f60b954da5f02cc2dba3\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"defe21f49bc98b095300752aa1e19bb608f3e97d\", \"lessThan\": \"57e2986c3b25092691a6e3d6ee9168caf8978932\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"defe21f49bc98b095300752aa1e19bb608f3e97d\", \"lessThan\": \"1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\", \"versionType\": \"git\"}], \"programFiles\": [\"arch/arm64/kvm/hyp/include/hyp/switch.h\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.11\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.11\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.22\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"5.16.8\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.16.*\"}, {\"status\": \"unaffected\", \"version\": \"5.17\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"arch/arm64/kvm/hyp/include/hyp/switch.h\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3\"}, {\"url\": \"https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932\"}, {\"url\": \"https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: arm64: Avoid consuming a stale esr value when SError occur\\n\\nWhen any exception other than an IRQ occurs, the CPU updates the ESR_EL2\\nregister with the exception syndrome. An SError may also become pending,\\nand will be synchronised by KVM. KVM notes the exception type, and whether\\nan SError was synchronised in exit_code.\\n\\nWhen an exception other than an IRQ occurs, fixup_guest_exit() updates\\nvcpu-\u003earch.fault.esr_el2 from the hardware register. When an SError was\\nsynchronised, the vcpu esr value is used to determine if the exception\\nwas due to an HVC. If so, ELR_EL2 is moved back one instruction. This\\nis so that KVM can process the SError first, and re-execute the HVC if\\nthe guest survives the SError.\\n\\nBut if an IRQ synchronises an SError, the vcpu\u0027s esr value is stale.\\nIf the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2,\\ncausing an unrelated guest instruction to be executed twice.\\n\\nCheck ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don\u0027t\\nupdate this register so don\u0027t need to check.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.22\", \"versionStartIncluding\": \"5.11\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.16.8\", \"versionStartIncluding\": \"5.11\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.17\", \"versionStartIncluding\": \"5.11\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T08:51:59.189Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2022-48727\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T08:51:59.189Z\", \"dateReserved\": \"2024-06-20T11:09:39.052Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-06-20T11:13:16.668Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.