Input: ims-pcu - check record size in ims_pcu_flash_firmware()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 628329d52474323938a03826941e166bc7c8eff4 · < 5a8cd6ae8393e2eaebf51d420d5374821ef2af87| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: ims-pcu - check record size in ims_pcu_flash_firmware()
The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);"
From the CVE record · Linux
The Linux kernel’s ims-pcu firmware flashing code does not check a record length supplied by firmware before copying data. If the length is too large, the copy can corrupt memory; the input does not specify how an attacker could supply the firmware or whether authentication or user interaction is required.
Engineers running the Linux kernel with the ims-pcu component should check their versions; affected versions were not provided.