Skip to main content
VulnerabilityPublished Updated

CVE-2026-43337: Linux kernel · drm/amd/display: Fix NULL pointer dereference in dcn401_init_hw()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in fcc51c81cb472eb460310c477460356dc4845ff7 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fcc51c81cb472eb460310c477460356dc4845ff7, e927b36ae18b66b49219eaa9f46edc7b4fdbb25e, 10c13c111d0d7f8e101c742feff264fc98e3f9f7 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.11.3 <6.12
Fixed in
  • fcc51c81cb472eb460310c477460356dc4845ff7
  • e927b36ae18b66b49219eaa9f46edc7b4fdbb25e
  • 10c13c111d0d7f8e101c742feff264fc98e3f9f7
  • 6.12
  • 2d4a6f0702c5211e0be8b688c5fc24f082ec74d6
LinuxLinuxAffected
  • =6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix NULL pointer dereference in dcn401_init_hw() dcn401_init_hw() assumes that update_bw_bounding_box() is valid when entering the update path. However, the existing condition: ((!fams2_enable && update_bw_bounding_box) || freq_changed) does not guarantee this, as the freq_changed branch can evaluate to true independently of the callback pointer. This can result in calling update_bw_bounding_box() when it is NULL. Fix this by separating the update condition from the pointer checks and ensuring the callback, dc->clk_mgr, and bw_params are validated before use. Fixes the below: ../dc/hwss/dcn401/dcn401_hwseq.c:367 dcn401_init_hw() error: we previously assumed 'dc->res_pool->funcs->update_bw_bounding_box' could be null (see line 362) (cherry picked from commit 86117c5ab42f21562fedb0a64bffea3ee5fcd477)

References

Community reviews

Loading reviews…