Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9 drm-amdgpu buffer overflow

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.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9. It has been classified as very critical. This issue affects some unknown processing of the component drm-amdgpu. Performing a manipulation results in buffer overflow. This vulnerability is reported as CVE-2026-80907. The attack requires a local approach. No exploit exists.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9. This affects an unknown code block of the component drm-amdgpu. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. 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/amdgpu: Fix UVD dpb min size calculation for H264 This should use actual number of references from the decode message, instead of maximum derived from level. (cherry picked from commit 64b525edb7e7bdfcdc77883c5e413804e2396856)

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-80907 since 08/26/2026. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/04/2026).

Upgrading to version 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch fa96c24485942e277483cc70d9551d9e0111d7c5/33f4ef585368fe93523dca1e5440e006f6e5146e/38914cb2c6afb5fe00241ea3438e655822196378/ff4361816b6ba4bd29b548b17d993056a1ae2502/21a8084cd76223a13493237e04d45f5226d7cee6 is able to eliminate this problem.

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: Buffer overflow
CWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

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.153/6.12.105/6.18.46/7.1.10
Patch: fa96c24485942e277483cc70d9551d9e0111d7c5/33f4ef585368fe93523dca1e5440e006f6e5146e/38914cb2c6afb5fe00241ea3438e655822196378/ff4361816b6ba4bd29b548b17d993056a1ae2502/21a8084cd76223a13493237e04d45f5226d7cee6

Timelineinfo

08/26/2026 CVE reserved
09/04/2026 +9 days Advisory disclosed
09/04/2026 +0 days VulDB entry created
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80907 (🔒)
GCVE (CVE): GCVE-0-2026-80907
GCVE (VulDB): GCVE-100-399117

Entryinfo

Created: 09/04/2026 19:47
Changes: 09/04/2026 19:47 (58)
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.

Might our Artificial Intelligence support you?

Check our Alexa App!