KernelScan.io

HIGH Introduced in 3.14

mxs-dcp Scatterlist OOB

CVE-2026-80831

CVSS 7.1 / 10.0 KernelScan AI

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

01

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.

02

Engine v0.6.0

Risk summary

The Freescale MXS DCP crypto driver uses an invalid scatterlist length when processing AES encryption/decryption requests, causing the wrong number of bytes to be processed. This can corrupt cryptographic output and potentially cause out-of-bounds memory access on systems with CONFIG_NEED_SG_DMA_LENGTH=y. Any local user with access to the crypto subsystem can trigger this.

Affecteddrivers/crypto/mxs-dcp.c (crypto: mxs-dcp)

Vulnerability analysis

The DCP crypto driver reads the DMA-mapped length of a source scatterlist entry before the scatterlist has been DMA-mapped, so the length field is uninitialized or stale. This causes the AES block cipher operation to process the wrong number of bytes, potentially reading or writing beyond the intended buffer boundaries. The fix switches to using the original scatterlist length field, which is always valid regardless of DMA mapping state. The vulnerable code path is reachable by any local user who can submit cryptographic requests through the kernel crypto framework on systems with the MXS DCP hardware enabled.

03

BranchIntroducedFixed inPatch commit
5.103.145.10.269fd0f211b27a6
5.153.145.15.22004201dcc88b2
6.13.146.1.187e72a795df521
6.123.146.12.108da14fae5203b
6.183.146.18.49182f16a20d32
6.63.146.6.1561537bd55b4f8
7.13.147.1.130e9edb108a63
7.23.147.2.36ef9a4afb52c
mainline3.147.3c5bcb084a987
cip/5.103.145.10.271-cip78fd0f211b27a6
cip/6.13.146.1.187-cip60e72a795df521
cip/6.1-rt3.146.1.189-cip61-rt32e72a795df521
cip/6.123.146.12.108-cip31da14fae5203b

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.108-cip31
cip/6.1Fixed in 6.1.187-cip60
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.271-cip78
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.268-cip77-rt34)
cip/4.19Affected — no CIP fix yet (latest 4.19.325-cip136)
cip/4.19-rtAffected — no CIP fix yet (latest 4.19.325-cip136-rt50)
cip/4.4Affected — no CIP fix yet (latest 4.4.302-cip115)
cip/4.4-rtAffected — no CIP fix yet (latest 4.4.302-cip115-rt63)