What is CVE-2022-48727?

CVE-2022-48727 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 5.11 onward and patched in 5.15.22, 5.16.8 and 5.17. CVE-2022-48727 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2022-48727?

CVE-2022-48727 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2022-48727?

Yes, CVE-2022-48727 has been patched. Fixed versions include 5.15.22, 5.16.8 and 5.17. If you are running Linux kernel 5.11 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2022-48727 actively exploited?

CVE-2022-48727 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2022-48727

Medium

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.

Package Linux Kernel

Published 2024-06-20

Last modified 2025-10-01

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 5.11 and later are affected. Fixed in 5.15.22, 5.16.8, 5.17 and their respective stable series.

Affected from

≥ 5.11

Fixed in

✓ 5.15.22 5.15.x ✓ 5.16.8 5.16.x ✓ 5.17

References

3 total

Kernel Git
https://git.kernel.org/stable/c/1c71dbc8a179d99dd9bb7e7fc1888db613cf85de

Patch
Kernel Git
https://git.kernel.org/stable/c/57e2986c3b25092691a6e3d6ee9168caf8978932

Patch
Kernel Git
https://git.kernel.org/stable/c/e1e852746997500f1873f60b954da5f02cc2dba3

Patch

Details

CVE ID CVE-2022-48727

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2024-06-20

Modified 2025-10-01

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2022-48727?

CVE-2022-48727 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 5.11 onward and has been patched in 5.15.22, 5.16.8 and 5.17. CVE-2022-48727 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2022-48727?

CVE-2022-48727 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2022-48727?

Yes. CVE-2022-48727 has been patched. Fixed versions include 5.15.22, 5.16.8 and 5.17. If you are running Linux kernel 5.11 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2022-48727 actively exploited?

No. CVE-2022-48727 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.