CVE-2025-38362
What it is
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null pointer check for get_first_active_display() The function mod_hdcp_hdcp1_enable_encryption() calls the function get_first_active_display(), but does not check its return value. The return value is a null pointer if the display list is empty. This will lead to a null pointer dereference in mod_hdcp_hdcp2_enable_encryption(). Add a null pointer check for get_first_active_display() and return MOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.187
- Linux Kernel < 6.1.143
- Linux Kernel < 6.6.96
- Linux Kernel < 6.12.36
- Linux Kernel < 6.15.5
- Debian Linux 11.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38362.md and follow it. Check whether this project is affected by CVE-2025-38362. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1ebcdf38887949def1a553ff3e45c98ed95a3cd0
- https://git.kernel.org/stable/c/34d3e10ab905f06445f8dbd8a3d9697095e71bae
- https://git.kernel.org/stable/c/4ce9f2dc9ff7cc410e8c5d936ec551e26b9599a9
- https://git.kernel.org/stable/c/5148c7ea69e9c5bf2f05081190f45ba96d3d1e7a
- https://git.kernel.org/stable/c/b3005145eab98d36777660b8893466e4f630ae1c
- https://git.kernel.org/stable/c/c3e9826a22027a21d998d3e64882fa377b613006
References
- https://git.kernel.org/stable/c/1ebcdf38887949def1a553ff3e45c98ed95a3cd0
- https://git.kernel.org/stable/c/34d3e10ab905f06445f8dbd8a3d9697095e71bae
- https://git.kernel.org/stable/c/4ce9f2dc9ff7cc410e8c5d936ec551e26b9599a9
- https://git.kernel.org/stable/c/5148c7ea69e9c5bf2f05081190f45ba96d3d1e7a
- https://git.kernel.org/stable/c/b3005145eab98d36777660b8893466e4f630ae1c
- https://git.kernel.org/stable/c/c3e9826a22027a21d998d3e64882fa377b613006
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html