Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49320

dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type In zynqmp_dma_alloc/free_chan_resources functions there is a potential overflow in the below expressions. dma_alloc_coherent(chan->dev, (2 * chan->desc_size * ZYNQMP_DMA_NUM_DESCS), &chan->desc_pool_p, GFP_KERNEL); dma_free_coherent(chan->dev,(2 * ZYNQMP_DMA_DESC_SIZE(chan) * ZYNQMP_DMA_NUM_DESCS), chan->desc_pool_v, chan->desc_pool_p); The arguments desc_size and ZYNQMP_DMA_NUM_DESCS were 32 bit. Though this overflow condition is not observed but it is a potential problem in the case of 32-bit multiplication. Hence fix it by changing the desc_size data type to size_t. In addition to coverity fix it also reuse ZYNQMP_DMA_DESC_SIZE macro in dma_alloc_coherent API argument. Addresses-Coverity: Event overflow_before_widen.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49320, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected b0cc417c1637192be658e68a74c8d1568e3d35f6 – < 83960276ffc9bf5570d4106490346b61e61be5f3
    • affected b0cc417c1637192be658e68a74c8d1568e3d35f6 – < 95a0ba85c1b51b36e909841c02d205cd223ab753
    • affected b0cc417c1637192be658e68a74c8d1568e3d35f6 – < 7b5488f4721fed6e121e661e165bab06ae2f8675
    • affected b0cc417c1637192be658e68a74c8d1568e3d35f6 – < 4838969e4d95d2bd2995d1605b20d3144fcb3e74
    • affected b0cc417c1637192be658e68a74c8d1568e3d35f6 – < 90aefae2e3a770a6909d339f5d8a988c0b0ceaf0
    • affected b0cc417c1637192be658e68a74c8d1568e3d35f6 – < f9a9f43a62a04ec3183fb0da9226c7706eed0115
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.122 – ≤ 5.10.*
    • unaffected 5.15.47 – ≤ 5.15.*
    • unaffected 5.17.15 – ≤ 5.17.*
    • unaffected 5.18.4 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49320 badge
[![CVE-2022-49320](https://cveledger.app/badge/CVE-2022-49320.svg)](https://cveledger.app/cve/CVE-2022-49320)

Record last updated .