CVE-2025-40165
BaseFortify
Publication date: 2025-11-12
Last updated on: 2025-11-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nxp | imx8-isi | * |
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 driver for NXP i.MX8 ISI (Image Signal Interface). If the streamon and streamoff calls are not balanced, such as when an application exits unexpectedly (e.g., with Ctrl+C during streaming), the usage count for the memory-to-memory (m2m) device does not reach zero, causing the ISI channel to remain allocated and not freed. Additionally, if the input line width exceeds 2K pixels, it triggers a kernel warning (WARN_ON). The issue was fixed by moving streaming preparation and cleanup to specific vb2 operations, simplifying the driver and ensuring proper resource cleanup.
How can this vulnerability impact me? :
This vulnerability can lead to resource leakage in the Linux kernel media driver, where the ISI channel remains allocated if streaming is interrupted improperly. This can cause system instability or degraded performance due to unreleased resources. The kernel warning triggered by large input widths may also indicate potential kernel crashes or unexpected behavior during video streaming operations.
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 kernel warnings related to the imx8-isi driver, specifically messages containing 'WARNING: drivers/media/platform/nxp/imx8-isi/imx8-isi-hw.c' and 'mxc_isi_channel_chain'. Checking dmesg output for such WARN_ON() traces can help identify the issue. For example, running the command 'dmesg | grep imx8-isi' or 'dmesg | grep WARNING' may reveal relevant warnings.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves ensuring that applications using the imx8-isi media driver properly balance streamon and streamoff calls to avoid leaving the m2m usage_count non-zero. Avoid forcibly terminating streaming applications (e.g., with Ctrl+C) without proper cleanup. Applying the updated Linux kernel version that includes the fix moving streaming preparation and cleanup to vb2 .prepare_streaming() and .unprepare_streaming() operations is recommended to fully resolve the issue.