CVE-2025-38348
wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()
Reported by linux · Published July 10, 2025
In the Linux kernel, the following vulnerability has been resolved: wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback() Robert Morris reported: |If a malicious USB device pretends to be an Intersil p54 wifi |interface and generates an eeprom_readback message with a large |eeprom->v1.len, p54_rx_eeprom_readback() will copy data from the |message beyond the end of priv->eeprom. | |static void p54_rx_eeprom_readback(struct p54_common *priv, | struct sk_buff *skb) |{ | struct p54_hdr *hdr = (struct p54_hdr *) skb->data; | struct p54_eeprom_lm86 *eeprom = (struct p54_eeprom_lm86 *) hdr->data; | | if (priv->fw_var >= 0x509) { | memcpy(priv->eeprom, eeprom->v2.data, | le16_to_cpu(eeprom->v2.len)); | } else { | memcpy(priv->eeprom, eeprom->v1.data, | le16_to_cpu(eeprom->v1.len)); | } | [...] The eeprom->v{1,2}.len is set by the driver in p54_download_eeprom(). The device is supposed to provide the same length back to the driver. But yes, it's possible (like shown in the report) to alter the value to something that causes a crash/panic due to overrun. This patch addresses the issue by adding the size to the common device context, so p54_rx_eeprom_readback no longer relies on possibly tampered values... That said, it also checks if the "firmware" altered the value and no longer copies them. The one, small saving grace is: Before the driver tries to read the eeprom, it needs to upload >a< firmware. the vendor firmware has a proprietary license and as a reason, it is not present on most distributions by default.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.15.4, 6.12.35, 6.6.95, 6.1.142, 5.15.186, 5.10.239, 5.4.295 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 7cb770729ba895f73253dfcd46c3fcba45d896f9, 7cb770729ba895f73253dfcd46c3fcba45d896f9, 7cb770729ba895f73253dfcd46c3fcba45d896f9 |
| Linux | Linux | 2.6.28, 0, 5.4.295 |
| linux | linux_kernel | 2.6.28, 2.6.28, 2.6.28 |
| Linux | Linux | 7cb770729ba895f73253dfcd46c3fcba45d896f9, 7cb770729ba895f73253dfcd46c3fcba45d896f9, 7cb770729ba895f73253dfcd46c3fcba45d896f9 |
Timeline
- Jul 9, 2025 CVE Published
- Jul 10, 2025 EPSS Score (30 in total, the first dated here)
- Oct 11, 2025 PoC Published (15 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (169 in total, the first dated here)
- Mar 29, 2026 Security Advisory (175 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
- Oct 7, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38348
vulnetix vdb fixes CVE-2025-38348
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38348/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart