Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68236drm/amd/display: set new_stream to NULL after release

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)

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68236, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < 92b7c6e3a1546c6db868b07e93fa6fb950d1d3a0
    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < bf9c06c70f496f1ba4474caf95c69696c828340e
    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < 01ba5b36898d6258f584269537cc49e7b05cf7c6
    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < ba8bf1dcbb44773e7a0fd13b42925c644e0d5e76
    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < 5182e442e61397d446c36995b8f5676942d35b82
    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < 679f23f0a3606afcef1ffabd72222f00a54ad9e3
    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < 0676fecbb5242aa22c057e78326d6d6041db034c
    • affected 9b690ef3c70422cdcd0cf912db33f2c92ef4a53f – < 9fa26b9eed6195bf840f39ac183b9a6237548755
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68236 badge
[![CVE-2026-68236](https://cveledger.app/badge/CVE-2026-68236.svg)](https://cveledger.app/cve/CVE-2026-68236)

Record last updated .