Linux Kernel up to 7.2-rc3 AMD Display drm/amd/display dm_update_crtc_state use after free

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

Summaryinfo

A vulnerability labeled as very critical has been found in Linux Kernel up to 6.6.147/6.12.100/6.18.41/7.1.5/7.2-rc3. This issue affects the function dm_update_crtc_state of the file drm/amd/display of the component AMD Display. The manipulation results in use after free. This vulnerability is known as CVE-2026-68236. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.147/6.12.100/6.18.41/7.1.5/7.2-rc3. It has been classified as very critical. Affected is the function dm_update_crtc_state of the file drm/amd/display of the component AMD Display. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: set new_stream to NULL after release In dm_update_crtc_state(), the skip_modeset path releases new_stream via dc_stream_release() but does not set the pointer to NULL. If a later error (e.g., color management failure) triggers the fail label, the error path calls dc_stream_release() again on the same dangling pointer, causing a double release and potential use-after-free. Fix this by setting new_stream to NULL after the initial release. (cherry picked from commit 99f3af19073b3ddbfd96e789124cce12c4277b28)

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-68236 since 07/30/2026. The exploitability is told to be easy. The attack needs to be approached locally. 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 08/10/2026).

Upgrading to version 6.6.148, 6.12.101, 6.18.42, 7.1.6 or 7.2-rc4 eliminates this vulnerability. Applying the patch ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76/5182e442e61397d446c36995b8f5676942d35b82/679f23f0a3606afcef1ffabd72222f00a54ad9e3/0676fecbb5242aa22c057e78326d6d6041db034c/9fa26b9eed6195bf840f39ac183b9a6237548755 is able to eliminate this problem.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

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: Use after free
CWE: CWE-416 / 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.148/6.12.101/6.18.42/7.1.6/7.2-rc4
Patch: ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76/5182e442e61397d446c36995b8f5676942d35b82/679f23f0a3606afcef1ffabd72222f00a54ad9e3/0676fecbb5242aa22c057e78326d6d6041db034c/9fa26b9eed6195bf840f39ac183b9a6237548755

Timelineinfo

07/30/2026 CVE reserved
08/10/2026 +11 days Advisory disclosed
08/10/2026 +0 days VulDB entry created
08/10/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-68236 (🔒)
GCVE (CVE): GCVE-0-2026-68236
GCVE (VulDB): GCVE-100-387600

Entryinfo

Created: 08/10/2026 16:35
Changes: 08/10/2026 16:35 (60)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

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!