Linux Kernel up to 6.12.117/6.18.63/7.3.4 vgic state issue

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.21+

Summaryinfo

A vulnerability marked as very critical has been reported in Linux Kernel up to 6.12.117/6.18.63/7.3.4. This issue affects some unknown processing of the component vgic. This manipulation causes state issue. This vulnerability appears as CVE-2026-99573. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as very critical was found in Linux Kernel up to 6.12.117/6.18.63/7.3.4. Affected by this vulnerability is an unknown code of the component vgic. The manipulation with an unknown input leads to a state issue vulnerability. The CWE definition for the vulnerability is CWE-371. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Stop the target vcpu when disabling LPIs Disabling LPIs is pretty nasty, as it directly messes with the AP list of the affected CPU, which could be running... This has the potential to lead to really bad behaviours, and we should not be doing that. Take example on the way the Active state is handled and simply pause the the vcpu so that we are sure it is in a quiescent state, and the state be safely manipulated. Nobody has any expectation of performance for this anyway.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-99573 since 09/25/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/20/2026).

Upgrading to version 6.12.118, 6.18.64, 7.3.5 or 7.4-rc1 eliminates this vulnerability. Applying the patch b5d4692948f2fc6cf6f1b7223bd10c3d1c3bb104/9b12da785bd0af7f0976ec24332f33634f7ee924/8f431c3829f38bacbf69447cbffda6968b260f5d/a1b4bd2c2c262b8094c86afb99364d16ac08cb66 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: State issue
CWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.118/6.18.64/7.3.5/7.4-rc1
Patch: b5d4692948f2fc6cf6f1b7223bd10c3d1c3bb104/9b12da785bd0af7f0976ec24332f33634f7ee924/8f431c3829f38bacbf69447cbffda6968b260f5d/a1b4bd2c2c262b8094c86afb99364d16ac08cb66

Timelineinfo

09/25/2026 CVE reserved
11/20/2026 +56 days Advisory disclosed
11/20/2026 +0 days VulDB entry created
11/20/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CNA: Linux
CVE: CVE-2026-99573 (🔒)

GCVE (CVE): GCVE-0-2026-99573
GCVE (VulDB): GCVE-100-440983

Entryinfo

Created: 11/20/2026 07:21
Changes: 11/20/2026 07:21 (58)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!