CVE-2026-53277

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation walk_s1() and kvm_walk_nested_s2() expect to be called while holding kvm->srcu to guard against memslot changes. While this is generally the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the respective walkers without taking kvm->srcu. Fix by acquiring kvm->srcu prior to the table walk in both instances.

CVSS v3.1 Score

8.8

HIGH

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

EPSS — Exploit Prediction

0.0011

Probability of exploitation

0.02%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-820 CWE-820

References

Other References

https://git.kernel.org/stable/c/97706097f9b851cfe55c3b00b083dfc2bcf542bc https://git.kernel.org/stable/c/ec42b4ed1b072ea2d03f086061aa67bad6d8de39 https://git.kernel.org/stable/c/f2ca45b50d4216c9cc7ffabf50d9ad1932209251 https://access.redhat.com/security/cve/CVE-2026-53277 https://bugzilla.redhat.com/show_bug.cgi?id=2492725 https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53277.json

Frequently Asked Questions

What is CVE-2026-53277? +

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation walk_s1() and kvm_walk_nested_s2() expect to be called while holding kvm->srcu to guard against memslot changes. While this is generally the case, __kvm_at_s12() and __kvm_find_s1_desc_level() call into the respective walkers without taking kvm->srcu. Fix by acquiring kvm->srcu prior to the table walk in both instances. It has a CVSS v3.1 base score of 8.8 (HIGH).

How severe is CVE-2026-53277? +

CVE-2026-53277 has a CVSS v3.1 score of 8.8 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0011, placing it in the 0th percentile for exploitation probability.

How do I check if I'm vulnerable to CVE-2026-53277? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2025-47154 9.0

LibJS in Ladybird before f5a6704 mishandles the freeing of the vector that arguments_list references, leading to a use-after-free, and allowing …

CVE-2024-49114 7.8

Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability

CVE-2026-53153 7.8

In the Linux kernel, the following vulnerability has been resolved: mm/list_lru: drain before clearing xarray entry on reparent memcg_reparent_list_lrus() clears …

CVE-2025-1445 7.5

A vulnerability exists in RTU IEC 61850 client and server functionality that could impact the availability if renegotiation of an …

CVE-2022-50238 7.4

The on-endpoint Microsoft vulnerable driver blocklist is not fully synchronized with the online Microsoft recommended driver block rules. Some entries …

CVE-2025-47999 6.8

Missing synchronization in Windows Hyper-V allows an authorized attacker to deny service over an adjacent network.