HIGH Introduced in 3.7
dmaengine ScatterList OOB
CVE-2026-98298
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
01Description
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.
02KernelScan AI Analysis
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.
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.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 5.10 | 3.7 | 5.10.271 | f448a5f5bd10 |
| 5.15 | 3.7 | 5.15.222 | 2148db529f08 |
| 6.1 | 3.7 | 6.1.189 | d920c07aa6d8 |
| 6.12 | 3.7 | 6.12.112 | 88a505330eb0 |
| 6.18 | 3.7 | 6.18.54 | bae65e492592 |
| 6.6 | 3.7 | 6.6.158 | 4a33886057e6 |
| 7.2 | 3.7 | 7.2.8 | 54ccc01012a2 |
| mainline | 3.7 | 7.3 | 075bc7b1d3dd |
| cip/4.19 | 3.7 | 4.19.325-cip137 | b019f279ca5f |
| cip/4.19-rt | 3.7 | 4.19.325-cip137-rt51 | b019f279ca5f |
| cip/4.4 | 3.7 | 4.4.302-cip116 | 17427f3f5e63 |
| cip/5.10 | 3.7 | 5.10.271-cip78 | f448a5f5bd10 |
| cip/5.10-rt | 3.7 | 5.10.272-cip79-rt35 | f448a5f5bd10 |
| cip/6.1 | 3.7 | 6.1.189-cip61 | d920c07aa6d8 |
| cip/6.1-rt | 3.7 | 6.1.189-cip61-rt32 | d920c07aa6d8 |
| cip/6.12 | 3.7 | 6.12.112-cip33 | 88a505330eb0 |
04CIP Kernels
State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.
| CIP tree | State |
|---|---|
| cip/6.12 | Fixed in 6.12.112-cip33 |
| cip/6.1 | Fixed in 6.1.189-cip61 |
| cip/6.1-rt | Fixed in 6.1.189-cip61-rt32 |
| cip/5.10 | Fixed in 5.10.271-cip78 |
| cip/5.10-rt | Fixed in 5.10.272-cip79-rt35 |
| cip/4.19 | Fixed in 4.19.325-cip137 |
| cip/4.19-rt | Fixed in 4.19.325-cip137-rt51 |
| cip/4.4 | Fixed in 4.4.302-cip116 |
| cip/4.4-rt | Affected — no CIP fix yet (latest 4.4.302-cip115-rt63) |