CVE-2026-68236 — drm/amd/display: set new_stream to NULL after release
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)
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < 92b7c6e3a1546c6db868b07e93fa6fb950d1d3a0≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < bf9c06c70f496f1ba4474caf95c69696c828340e≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < 01ba5b36898d6258f584269537cc49e7b05cf7c6≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < 5182e442e61397d446c36995b8f5676942d35b82≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < 679f23f0a3606afcef1ffabd72222f00a54ad9e3≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < 0676fecbb5242aa22c057e78326d6d6041db034c≥ 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f and < 9fa26b9eed6195bf840f39ac183b9a6237548755 and 1 moreversion 4.15 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/679f23f0a3606afcef1ffabd72222f00a54ad9e3
- git.kernel.org/stable/c/ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76
- git.kernel.org/stable/c/01ba5b36898d6258f584269537cc49e7b05cf7c6
- git.kernel.org/stable/c/bf9c06c70f496f1ba4474caf95c69696c828340e
- git.kernel.org/stable/c/0676fecbb5242aa22c057e78326d6d6041db034c
- git.kernel.org/stable/c/5182e442e61397d446c36995b8f5676942d35b82
- git.kernel.org/stable/c/9fa26b9eed6195bf840f39ac183b9a6237548755
- git.kernel.org/stable/c/92b7c6e3a1546c6db868b07e93fa6fb950d1d3a0
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 16h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 16h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68236 is "drm/amd/display: set new_stream to NULL after release", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.