CVE-2026-46216: drm/xe/hdcp: Add NULL check for media_gt in intel_hdcp_gsc_check_status()
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/hdcp: Add NULL check for media_gt in intel_hdcp_gsc_check_status()
When media GT is disabled via configfs, there is no allocation for
media_gt, which is kept as NULL. In such scenario,
intel_hdcp_gsc_check_status() results in a kernel pagefault error due to
>->uc.gsc being evaluated as an invalid memory address.
Fix that by introducing a NULL check on media_gt and bailing out early
if so.
While at it, also drop the NULL check for gsc, since it can't be NULL if
media_gt is not NULL.
v2:
- Get address for gsc only after checking that gt is not NULL.
(Shuicheng)
- Drop the NULL check for gsc. (Shuicheng)
v3:
- Add "Fixes" and "Cc: <stable...>" tags. (Matt)
(cherry picked from commit bfaf87e84ca3ca3f6e275f9ae56da47a8b55ffd1)
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause a kernel page fault when the Intel xe HDCP status path runs while media GT has been disabled through configfs. The source describes a missing NULL check, not data theft or code execution. Business impact appears primarily availability-related, but severity is not scored in the provided sources.
Executive priority
Schedule normal-to-expedited kernel patching for affected Linux graphics workloads. Escalate only if the affected systems are business-critical, exposed to untrusted local users, or vendor advisories later confirm broader impact or exploitation.
Technical view
In drm/xe/hdcp, intel_hdcp_gsc_check_status() could dereference media_gt when it is NULL. The NULL state occurs when media GT is disabled via configfs, leaving no media_gt allocation. Stable fixes add an early NULL check and remove an unnecessary gsc NULL check once media_gt is confirmed present.
Likely exposure
Exposure is most likely on Linux systems using the Intel xe graphics driver and HDCP/GSC-related paths, especially where media GT can be disabled via configfs. Distribution kernels may differ because vendors backport fixes, so package-level verification is required.
Exploitation context
The provided sources do not report active exploitation, public exploit code, or KEV listing. The described trigger is a specific kernel configuration/runtime state leading to a page fault. Treat this as a stability and local availability concern unless vendor advisories add stronger impact evidence.
Researcher notes
Evidence is limited to the kernel resolution text and stable commit references. No CVSS, CWE, exploit status, or detailed attack preconditions are provided. Analysis should stay anchored to NULL pointer dereference/page fault behavior in the xe HDCP GSC status path.
Mitigation direction
Update to a vendor kernel containing the referenced stable NULL-check fix.
Check distribution advisories for CVE-2026-46216 package status.
Prioritize systems with Intel xe graphics and HDCP/GSC exposure.
If updates are unavailable, follow vendor guidance before changing graphics configuration.
Validation and detection
Inventory Linux kernel versions and distribution backport status.
Check changelogs for CVE-2026-46216 or referenced stable commit IDs.
Confirm whether drm/xe is present and loaded on target systems.
Review whether media GT is disabled through configfs on affected hosts.
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-2026-46216 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 28, 2026, 09:40 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.