crypto: cavium - prevent integer overflow loading firmware
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9e2c7d99941d000a36f68a3594cec27a1bbea274 · < 371fa5129af53a79f6dddc90fe5bb0825cbe72a4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: cavium - prevent integer overflow loading firmware
The "code_length" value comes from the firmware file. If your firmware is untrusted realistically there is probably very little you can do to protect yourself. Still we try to limit the damage as much as possible. Also Smatch marks any data read from the filesystem as untrusted and prints warnings if it not capped correctly.
The "ntohl(ucode->code_length) * 2" multiplication can have an integer overflow.
From the CVE record · Linux
The Linux kernel's cavium crypto driver can overflow an integer when calculating a length from a firmware file. An attacker who can supply untrusted firmware could trigger the overflow during firmware loading; the input does not specify a further impact or authentication requirements.
Engineers running Linux kernels that use the cavium crypto driver should check their installations; affected versions are not specified.