crypto: mxs-dcp - fix source scatterlist length access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 15b59e7c3733f90ff1f7dd66ad77ae1c90bcdff5 · < 182f16a20d329a1c818d51dad57d9bf43d356c7c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: mxs-dcp - fix source scatterlist length access
mxs_dcp_aes_block_crypt() uses sg_dma_len() without mapping the source scatterlist with dma_map_sg() first. Therefore, sg_dma_len() is invalid and could return zero or a stale DMA length, causing encryption and decryption to process the wrong number of bytes when CONFIG_NEED_SG_DMA_LENGTH=y.
Use the original scatterlist length instead.
From the CVE record · Linux
The Linux kernel's mxs-dcp AES code reads a DMA scatterlist length before mapping the source scatterlist. When CONFIG_NEED_SG_DMA_LENGTH=y, this can cause encryption or decryption to process the wrong number of bytes. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the mxs-dcp driver and CONFIG_NEED_SG_DMA_LENGTH=y should check their affected versions.