CVE-2025-39739
BaseFortify
Publication date: 2025-09-11
Last updated on: 2025-11-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves the Linux kernel's handling of certain Qualcomm IOMMU (Input-Output Memory Management Unit) devices, specifically the arm-smmu-qcom driver. The issue is that the SM6115 MDSS compatible device was not included in the clients compatible list, which caused many unhandled context faults during boot on devices like QRB4210 RB2 based on SM4250/SM6115. These faults lead to failures in initializing components such as the lontium lt9611uxc, GPU, and DPU, resulting in errors and failed bindings during system startup. The vulnerability was fixed by adding the SM6115 MDSS compatible to the clients compatible list to apply the necessary workaround.
How can this vulnerability impact me? :
This vulnerability can cause numerous unhandled context faults during system boot, leading to failures in initializing critical hardware components like the GPU, display processing unit (DPU), and certain display interfaces (e.g., lontium lt9611uxc). As a result, devices affected by this issue may experience boot failures, degraded graphics performance, or complete failure to initialize display hardware, which can severely impact device usability and stability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for specific error messages related to the arm-smmu context faults and GPU initialization failures. Look for messages such as 'arm_smmu_context_fault', 'Unhandled context fault', and errors related to 'lt9611uxc' or 'msm_dpu' during boot or runtime. Commands to check the kernel log include: 'dmesg | grep arm_smmu_context_fault', 'dmesg | grep Unhandled context fault', and 'dmesg | grep lt9611uxc'. These commands help identify the presence of the fault and failed initialization indicative of the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the kernel patch that adds the SM6115 MDSS compatible to the clients compatible list, which includes the necessary workaround to prevent the unhandled context faults and initialization failures. Until the patch is applied, monitoring for the fault messages and avoiding affected hardware configurations may reduce impact. Updating the Linux kernel to a version that includes this fix is the recommended step.