CVE-2025-38348wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.21% · top 89% of all CVEs (14 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

• Linux · Linux

  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < 12134f79e53eb56b0b0b7447fa0c512acf6a8422
  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < 9701f842031b825e2fd5f22d064166f8f13f6e4d
  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < 1f7f8168abe8cbe845ab8bb557228d44784a6b57
  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < f39b2f8c1549a539846e083790fad396ef6cd802
  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < 0e4dc150423b829c35cbcf399481ca11594fc036
  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < 6d05390d20f110de37d051a3e063ef0a542d01fb
  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < 714afb4c38edd19a057d519c1f9c5d164b43de94
  • affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 – < da1b9a55ff116cb040528ef664c70a4eec03ae99

• Linux · Linux

  • affected 2.6.28
  • unaffected < 2.6.28
  • unaffected 5.4.295 – ≤ 5.4.*
  • unaffected 5.10.239 – ≤ 5.10.*
  • unaffected 5.15.186 – ≤ 5.15.*
  • unaffected 6.1.142 – ≤ 6.1.*
  • unaffected 6.6.95 – ≤ 6.6.*
  • unaffected 6.12.35 – ≤ 6.12.*
  • unaffected 6.15.4 – ≤ 6.15.*
  • unaffected 6.16 – ≤ *

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2025-20898 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2025-38348](https://cveledger.app/badge/CVE-2025-38348.svg)](https://cveledger.app/cve/CVE-2025-38348)

Record last updated 11 May 2026, 21:26 UTC.