Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5 KVM arm64 handle_tlbi_el1 numeric range comparison without minimum check

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$0-$5k0.00-

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5. It has been declared as very critical. This impacts the function handle_tlbi_el1 of the component KVM arm64. The manipulation results in numeric range comparison without minimum check. This vulnerability is known as CVE-2026-98713. It is possible to launch the attack remotely. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.112/6.18.55/7.2.9/7.3-rc5. It has been classified as very critical. Affected is the function handle_tlbi_el1 of the component KVM arm64. The manipulation with an unknown input leads to a numeric range comparison without minimum check vulnerability. CWE is classifying the issue as CWE-839. The product checks a value to ensure that it is less than or equal to a maximum, but it does not also verify that the value is greater than or equal to the minimum. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Apply the fine-grained UNDEFs without FEAT_FGT FGUs don't actually require hardware support, so don't gate fgt trap config insertion on FGT. This is the only action required to allow FGUs always, as kvm_calculate_traps() already computes the FGU bits with or without FEAT_FGT. This also fixes a spurious WARN when a TLBI OS is run on a guest in vEL1 without FEAT_TLBIOS on non FEAT_FGT hardware. In this configuration the course-grained HCR_EL2.TTLBOS trap reaches the handler handle_tlbi_el1(), which expects an EL1 TLBI only from vEL2. With FGUs enabled the UNDEF will be injected without needing the specific handler. [oliver: Take Wei-Lin's suggested changelog]

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-98713 since 09/25/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/18/2026).

Upgrading to version 6.12.113, 6.18.56, 7.2.10 or 7.3-rc6 eliminates this vulnerability. Applying the patch 2f4a15c52a552c5244ec27f4ca8bda855594f918/1113374a17d7f7d16b02ee0bbd9b1e7a60cbb087/af3300b3a6bace925a496f3520e171c07b999c72/4bdd2b3a708c1feb701cb8b62feb8ad2fd77bb07 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best 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: Numeric range comparison without minimum check
CWE: CWE-839 / CWE-118
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.113/6.18.56/7.2.10/7.3-rc6
Patch: 2f4a15c52a552c5244ec27f4ca8bda855594f918/1113374a17d7f7d16b02ee0bbd9b1e7a60cbb087/af3300b3a6bace925a496f3520e171c07b999c72/4bdd2b3a708c1feb701cb8b62feb8ad2fd77bb07

Timelineinfo

09/25/2026 CVE reserved
10/18/2026 +23 days Advisory disclosed
10/18/2026 +0 days VulDB entry created
10/18/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-98713 (🔒)
GCVE (CVE): GCVE-0-2026-98713
GCVE (VulDB): GCVE-100-421980

Entryinfo

Created: 10/18/2026 19:38
Changes: 10/18/2026 19:38 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!