CVE-2025-38662
BaseFortify
Publication date: 2025-08-22
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 | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| 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-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a coding error in the Linux kernel's ASoC mediatek mt8365-dai-i2s driver where an incorrect size is passed to the function mt8365_dai_set_priv. The function allocates memory based on a certain structure size but copies data using a different, larger structure size, leading to a global out-of-bounds memory access detected by KASAN (Kernel Address Sanitizer). This means the kernel may read or write beyond allocated memory, causing instability or crashes.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to experience memory corruption due to out-of-bounds access, potentially leading to system crashes, instability, or unexpected behavior in devices using the affected mediatek mt8365 audio driver. It may also expose the system to security risks if exploited, such as privilege escalation or denial of service.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the kernel logs for KASAN (Kernel Address Sanitizer) reports indicating a global-out-of-bounds error in mt8365_dai_set_priv. You can use the command 'dmesg | grep KASAN' or 'journalctl -k | grep KASAN' to look for such error messages in the system logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the vulnerability is fixed, specifically where mt8365_dai_set_priv passes the correct size and data structure to avoid KASAN complaints. Until then, monitoring kernel logs for KASAN errors and avoiding use of affected components may help reduce risk.