Vulnerability · CVE-2023-53319
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle kvm_arm_init failure correctly in finalize_pkvm Currently there is no synchronisation between
Published Sep 16, 2025 · catalog updated May 11, 2026 · Linux Linux
Check if you run it
No confirmed exploitation is on record for CVE-2023-53319. EPSS is 0.14%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium5.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.14%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux 87727ba2bb05cc3cb4233231faa7ab4c7eeb6c73 <91450dec0445f4d12f960ba68d8d05c3cb2ab5b8
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle kvm_arm_init failure correctly in finalize_pkvm Currently there is no synchronisation between finalize_pkvm() and kvm_arm_init() initcalls. The finalize_pkvm() proceeds happily even if kvm_arm_init() fails resulting in the following warning on all the CPUs and eventually a HYP panic: | kvm [1]: IPA Size Limit: 48 bits | kvm [1]: Failed to init hyp memory protection | kvm [1]: error initializing Hyp mode: -22 | | | | WARNING: CPU: 0 PID: 0 at arch/arm64/kvm/pkvm.c:226 _kvm_host_prot_finalize+0x30/0x50 | Modul
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux 87727ba2bb05cc3cb4233231faa7ab4c7eeb6c73 <91450dec0445f4d12f960ba68d8d05c3cb2ab5b887727ba2bb05cc3cb4233231faa7ab4c7eeb6c73 <91450dec0445f4d12f960ba68d8d05c3cb2ab5b8
How to fix CVE-2023-53319
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2023-53319. EPSS is 0.14%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Linux Linux 87727ba2bb05cc3cb4233231faa7ab4c7eeb6c73 <91450dec0445f4d12f960ba68d8d05c3cb2ab5b8 87727ba2bb05cc3cb4233231faa7ab4c7eeb6c73 <91450dec0445f4d12f960ba68d8d05c3cb2ab5b8. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.14%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 16, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle kvm_arm_init failure correctly in finalize_pkvm Currently there is no synchronisation between finalize_pkvm() and kvm_arm_init() initcalls. The finalize_pkvm() proceeds happily even if kvm_arm_init() fails resulting in the following warning on all the CPUs and eventually a HYP panic: | kvm [1]: IPA Size Limit: 4
May 11, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle kvm_arm_init failure correctly in finalize_pkvm Currently there is no synchronisation between finalize_pkvm() and kvm_arm_init() initcalls. The finalize_pkvm() proceeds happily even if kvm_arm_init() fails resulting in the following warning on all the CPUs and eventually a HYP panic: | kvm [1]: IPA Size Limit: 4
Sources
- CVE.orgVulnerability recordCVE-2023-53319
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2023-53319
30-day exploitation probability 0.14%
first.org - EUVDVulnerability recordEUVD-2023-59942
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Handle kvm_arm_init failure correctly in finalize_pkvm Currently there is no synchronisation between finalize_pkvm() and kvm_arm_init() initcalls. The finalize_pkvm() proceeds happily even if kvm_arm_
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.