Linux Kernel up to 6.6.159/6.12.112/6.18.56/7.2.10 GEM Exec Buffer drm/i915/gem eb_relocate_parse_slow buffer_count array index

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

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 6.6.159/6.12.112/6.18.56/7.2.10. Affected is the function eb_relocate_parse_slow of the file drm/i915/gem of the component GEM Exec Buffer. Performing a manipulation of the argument buffer_count results in array index. This vulnerability was named CVE-2026-99006. The attack needs to be approached locally. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 6.6.159/6.12.112/6.18.56/7.2.10. This affects the function eb_relocate_parse_slow of the file drm/i915/gem of the component GEM Exec Buffer. The manipulation of the argument buffer_count with an unknown input leads to a array index vulnerability. CWE is classifying the issue as CWE-129. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gem: Prevent overstepping exec array boundary It is possible for eb_relocate_parse_slow() to call kvfree() on entries outside the original exec array during following scenario inside eb_relocate_parse_slow(): 1) eb_copy_relocations() allocates as many as eb->buffer_count copies for exec entries; 2) eb_parse() appends up to two VMAs, right after incrementing eb->buffer_count; 3) cleanup under "out" label uses this incremented buffer_count to release relocation pointers from exec array via kvfree(), not from VMA array. To amend this problem, ensure that relocation cleanup uses the original exec object count, excluding the VMAs appended by the command parser. (cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-99006 since 09/25/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/23/2026).

Upgrading to version 6.6.160, 6.12.113, 6.18.57 or 7.2.11 eliminates this vulnerability. Applying the patch 24c04e80c35ff36947366f6deafddb522eea080c/b1c357131fc467c579f65e9a9d1fdc1a6273ae1d/152fb5083b9333a1cb8629572f9e0f276a404ba6/72d5cbb10d4916a3f8ef9da516c5c0634aca8439/ebe162db655881a38de43301151ff7ac940602b5 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Array index
CWE: CWE-129 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

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.6.160/6.12.113/6.18.57/7.2.11
Patch: 24c04e80c35ff36947366f6deafddb522eea080c/b1c357131fc467c579f65e9a9d1fdc1a6273ae1d/152fb5083b9333a1cb8629572f9e0f276a404ba6/72d5cbb10d4916a3f8ef9da516c5c0634aca8439/ebe162db655881a38de43301151ff7ac940602b5

Timelineinfo

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

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-99006 (🔒)
GCVE (CVE): GCVE-0-2026-99006
GCVE (VulDB): GCVE-100-425853

Entryinfo

Created: 10/23/2026 15:41
Changes: 10/23/2026 15:41 (61)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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!