CVE-2026-98298
dmaengine: mmp_pdma: fix wrong sg length in mmp_pdma_prep_slave_sg()
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ c8acd6aa6bed3c0fd7898202f4ebc534db9085f2, < f448a5f5bd10d792440a1b08cf2e8f311767032dUpgrade to: f448a5f5bd10d792440a1b08cf2e8f311767032dAffected: ≥ c8acd6aa6bed3c0fd7898202f4ebc534db9085f2, < 2148db529f082d6e3ca95413bf943442f4ef30ccUpgrade to: 2148db529f082d6e3ca95413bf943442f4ef30ccAffected: ≥ c8acd6aa6bed3c0fd7898202f4ebc534db9085f2, < d920c07aa6d89ec11afdb6976aafaee9563a5234Upgrade to: d920c07aa6d89ec11afdb6976aafaee9563a5234Affected: ≥ c8acd6aa6bed3c0fd7898202f4ebc534db9085f2, < 4a33886057e6d127555efb022879c583e966acc5Upgrade to: 4a33886057e6d127555efb022879c583e966acc5 + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/f448a5f5bd10d792440a1b08cf2e8f311767032d
- git.kernel.org/stable/c/2148db529f082d6e3ca95413bf943442f4ef30cc
- git.kernel.org/stable/c/d920c07aa6d89ec11afdb6976aafaee9563a5234
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI