KernelScan.io

HIGH Introduced in 3.7

dmaengine ScatterList OOB

CVE-2026-98298

CVSS 7.3 / 10.0 KernelScan AI

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

01

In the Linux kernel, the following vulnerability has been resolved: dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg() In mmp_pdma_prep_slave_sg(), for_each_sg() iterates the scatterlist putting each entry into 'sg', but the entry length is read from 'sgl' (the list head) instead of 'sg' (the current entry): for_each_sg(sgl, sg, sg_len, i) { addr = sg_dma_address(sg); avail = sg_dma_len(sgl); /* should be 'sg' */ Consequently 'avail' is always the length of the first entry. For multi-sg lists this causes out-of-bounds reads when a later entry is shorter than the first, and silent data loss when it is longer. Single-sg or uniformly-sized lists happen to mask the issue.

02

Engine v0.7.0

Risk summary

A local user on a device with a Marvell MMP/PXA DMA controller can trigger out-of-bounds reads and silent data corruption by initiating DMA transfers with multi-entry scatterlists of varying sizes. The bug leaks adjacent kernel memory to peripheral devices and truncates transfers, with impact limited to systems using this specific SoC DMA engine.

Affecteddrivers/dma/mmp_pdma.c (dmaengine mmp_pdma)

Vulnerability analysis

The driver sets up slave DMA transfers by walking through a list of memory buffers, but it mistakenly applies the size of the first buffer to every other buffer in the list. This causes the DMA controller to read past the end of smaller buffers, leaking adjacent kernel memory to the peripheral device, and to transfer too little data when a buffer is larger, silently dropping data. The corrected driver now uses each buffer's actual size when programming the transfer. A local user who can operate peripherals backed by this Marvell DMA controller can trigger the flaw by submitting a DMA request that spans multiple buffers of different sizes.

03

BranchIntroducedFixed inPatch commit
5.103.75.10.271f448a5f5bd10
5.153.75.15.2222148db529f08
6.13.76.1.189d920c07aa6d8
6.123.76.12.11288a505330eb0
6.183.76.18.54bae65e492592
6.63.76.6.1584a33886057e6
7.23.77.2.854ccc01012a2
mainline3.77.3075bc7b1d3dd
cip/4.193.74.19.325-cip137b019f279ca5f
cip/4.19-rt3.74.19.325-cip137-rt51b019f279ca5f
cip/4.43.74.4.302-cip11617427f3f5e63
cip/5.103.75.10.271-cip78f448a5f5bd10
cip/5.10-rt3.75.10.272-cip79-rt35f448a5f5bd10
cip/6.13.76.1.189-cip61d920c07aa6d8
cip/6.1-rt3.76.1.189-cip61-rt32d920c07aa6d8
cip/6.123.76.12.112-cip3388a505330eb0

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.112-cip33
cip/6.1Fixed in 6.1.189-cip61
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.271-cip78
cip/5.10-rtFixed in 5.10.272-cip79-rt35
cip/4.19Fixed in 4.19.325-cip137
cip/4.19-rtFixed in 4.19.325-cip137-rt51
cip/4.4Fixed in 4.4.302-cip116
cip/4.4-rtAffected — no CIP fix yet (latest 4.4.302-cip115-rt63)