CVE-2025-38410: drm/msm: Fix a fence leak in submit error path
Published Jul 25, 2025
·Updated
drm/msm: Fix a fence leak in submit error path
Affected Software
13 affected componentsFixes available
Linux Kernel
Linux Linux kernel>=3.12<5.15.187
Linux Linux kernel>=5.16<6.1.144
Linux Linux kernel>=6.2<6.6.97
Linux Linux kernel>=6.7<6.12.37
Linux Linux kernel>=6.13<6.15.6
Linux Linux kernel=6.16-rc1
Linux Linux kernel=6.16-rc2
Debian Debian Linux=11.0
Microsoft azl3 kernel 6.6.96.2-1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft cbl2 kernel 5.15.186.1-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Jul 25, 2025
CVE Published
via MITRE·01:20 PM
Data Sourced
via MITRE·01:20 PM
Description
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 3, 2025
Data Sourced
via Microsoft·11:28 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-38410?
The severity of CVE-2025-38410 is categorized as medium due to the potential impact on system stability.
2
How do I fix CVE-2025-38410?
To fix CVE-2025-38410, update your Linux kernel to the latest patched version.
3
What systems are affected by CVE-2025-38410?
CVE-2025-38410 affects the Linux kernel, particularly systems utilizing the msm graphics driver.
4
What are the potential risks of CVE-2025-38410?
The potential risks include memory leaks and system instability during error handling in graphics processing.
5
When was CVE-2025-38410 reported?
CVE-2025-38410 was reported in 2025, following vulnerability assessments of the Linux kernel.