CVE-2025-40208
BaseFortify
Publication date: 2025-11-12
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qcom | iris | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's media component related to the qcom-iris video codec driver. It involves improper handling during module removal if the firmware download fails. Specifically, if the firmware fails to load, attempts to remove the module trigger runtime power management usage count underflows and warnings/errors related to clock disable/unprepare operations. The fix ensures that the deinitialization process is skipped if the initialization never succeeded, preventing these errors.
How can this vulnerability impact me? :
This vulnerability can cause runtime power management usage count underflows and warnings/errors during module removal if the firmware download fails. This may lead to instability or unexpected behavior in the media subsystem, potentially causing system warnings, errors, or crashes related to the qcom-iris video codec driver.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for error messages related to the qcom-iris video codec firmware loading failure and runtime PM usage count underflow in the system logs. You can look for messages like 'Direct firmware load for qcom/vpu/vpu33_p4.mbn failed with error -2', 'firmware download failed', and warnings about 'Runtime PM usage count underflow' in the kernel logs. A suggested command to check the kernel log for these errors is: dmesg | grep -E 'qcom-iris|firmware download failed|Runtime PM usage count underflow'. Additionally, the command to trigger the issue is: echo aa00000.video-codec > /sys/bus/platform/drivers/qcom-iris/unbind
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to apply the fix that prevents module removal if the firmware download failed, effectively skipping deinitialization if initialization never succeeded. Until the fix is applied, avoid unbinding the qcom-iris driver when firmware loading has failed to prevent runtime PM usage count underflow and related warnings. Monitoring and updating the Linux kernel to a version that includes this fix is recommended.