CVE-2025-38098: drm/amd/display: Don't treat wb connector as physical in create_validate_stream_for_sink
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Don't treat wb connector as physical in create_validate_stream_for_sink
Don't try to operate on a drm_wb_connector as an amdgpu_dm_connector.
While dereferencing aconnector->base will "work" it's wrong and
might lead to unknown bad things. Just... don't.
Security readout for executives and security teams
Plain-English summary
A Linux AMD display driver path can mistake a writeback connector for a physical AMD GPU connector. This incorrect type handling could cause serious kernel-level consequences. The supplied CVSS score is 7.8, requiring local low-privileged access, but the sources do not demonstrate a working exploit or confirm attacks.
Executive priority
Treat as a high-priority kernel maintenance issue on AMD graphics systems with untrusted local users. Schedule prompt patching, while recognizing that the supplied evidence does not show active exploitation or remotely reachable exposure.
Technical view
In create_validate_stream_for_sink, drm/amd/display could operate on a drm_wb_connector as though it were an amdgpu_dm_connector and dereference the incompatible connector structure. The record warns of unspecified harmful consequences. CVSS 3.1 rates potential confidentiality, integrity, and availability impact high, although no specific corruption primitive is documented.
Likely exposure
Potential exposure is limited to affected Linux kernels using the AMD display subsystem where the writeback-connector path is reachable. The bundle identifies releases including 6.8, 6.12.31, 6.14.9, and 6.15 as affected, but does not clearly express complete version ranges or vendor backport status.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. This CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation, public exploit availability, or reliable practical exploitation.
Researcher notes
No CWE is assigned. The flaw is an invalid connector-type assumption involving drm_wb_connector and amdgpu_dm_connector. The sources provide stable-kernel fixes but do not establish the precise failure mode, a memory-corruption primitive, affected configuration prerequisites, exploit reliability, or comprehensive downstream package mappings.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix or backport.
Review Linux distribution advisories to determine the corrected package for each deployed release.
Prioritize systems with AMD graphics and locally accessible untrusted users.
Apply normal kernel update procedures and reboot into the corrected kernel.
Validation and detection
Inventory running kernel versions and systems using the AMD display driver.
Confirm distribution package changelogs explicitly reference CVE-2025-38098 or a cited fix commit.
Verify the corrected kernel is active after reboot, not merely installed.
Review kernel logs for AMD display faults before and after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38098 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.