Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < 12134f79e53eb56b0b0b7447fa0c512acf6a8422; >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < 9701f842031b825e2fd5f22d064166f8f13f6e4d; >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < 1f7f8168abe8cbe845ab8bb557228d44784a6b57; >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < f39b2f8c1549a539846e083790fad396ef6cd802; >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < 0e4dc150423b829c35cbcf399481ca11594fc036; >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < 6d05390d20f110de37d051a3e063ef0a542d01fb; >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < 714afb4c38edd19a057d519c1f9c5d164b43de94; >= 7cb770729ba895f73253dfcd46c3fcba45d896f9, < da1b9a55ff116cb040528ef664c70a4eec03ae99 |
| Linux | Linux | 2.6.28 |
References
- https://git.kernel.org/stable/c/0e4dc150423b829c35cbcf399481ca11594fc036Patch
- https://git.kernel.org/stable/c/12134f79e53eb56b0b0b7447fa0c512acf6a8422Patch
- https://git.kernel.org/stable/c/1f7f8168abe8cbe845ab8bb557228d44784a6b57Patch
- https://git.kernel.org/stable/c/6d05390d20f110de37d051a3e063ef0a542d01fbPatch
- https://git.kernel.org/stable/c/714afb4c38edd19a057d519c1f9c5d164b43de94Patch
- https://git.kernel.org/stable/c/9701f842031b825e2fd5f22d064166f8f13f6e4dPatch
- https://git.kernel.org/stable/c/da1b9a55ff116cb040528ef664c70a4eec03ae99Patch
- https://git.kernel.org/stable/c/f39b2f8c1549a539846e083790fad396ef6cd802Patch
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlThird Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
Timeline
- Published
- Jul 10, 2025
- Last modified
- Jun 17, 2026
- NVD status
- Analyzed