CVE-2025-38348
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-12-16
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.11 (inc) to 5.15.186 (inc) |
| debian | debian_linux | 11.0 |
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 buffer overflow in the Linux kernel's p54 wifi driver, specifically in the function p54_rx_eeprom_readback(). A malicious USB device pretending to be an Intersil p54 wifi interface can send a crafted eeprom_readback message with an abnormally large length value. This causes the driver to copy more data than the allocated buffer size, leading to a buffer overflow. The issue arises because the driver trusts the length value provided by the device, which can be tampered with. The patch fixes this by using a size stored in the device context rather than the potentially tampered length, and by checking if the firmware altered the value before copying.
How can this vulnerability impact me? :
This vulnerability can cause a system crash or kernel panic due to the buffer overflow when a malicious USB device sends a specially crafted message. This could lead to denial of service or potentially allow an attacker to execute arbitrary code with kernel privileges if exploited further.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure your Linux kernel is updated to a version that includes the patch preventing buffer overflow in p54_rx_eeprom_readback(). Avoid connecting untrusted or potentially malicious USB devices that may impersonate an Intersil p54 wifi interface. Since the vulnerability involves a proprietary firmware not present by default on most distributions, verifying firmware integrity and applying vendor updates when available is also recommended.