crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 74ed87e7e7f7197137164738dd0610ccd5ec5ed1 · < 2ed27b5a1174351148c3adbfc0cd86d54072ba2e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly
The existing allocation of scatterlists in omap_crypto_copy_sg_lists() was allocating an array of scatterlist pointers, not scatterlist objects, resulting in a 4x too small allocation.
Use sizeof(*new_sg) to get the correct object size.
From the CVE record · Linux
The Linux kernel's OMAP crypto code allocates too little memory for scatterlist objects in omap_crypto_copy_sg_lists(). The input does not specify what an attacker could do or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with the OMAP crypto code should check their deployments; affected versions are not specified.