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-2023-54255sh: dma: Fix DMA channel offset calculation

Description

In the Linux kernel, the following vulnerability has been resolved: sh: dma: Fix DMA channel offset calculation Various SoCs of the SH3, SH4 and SH4A family, which use this driver, feature a differing number of DMA channels, which can be distributed between up to two DMAC modules. The existing implementation fails to correctly accommodate for all those variations, resulting in wrong channel offset calculations and leading to kernel panics. Rewrite dma_base_addr() in order to properly calculate channel offsets in a DMAC module. Fix dmaor_read_reg() and dmaor_write_reg(), so that the correct DMAC module base is selected for the DMAOR register.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < bca700b48c72f4ffeee977a2ed0eb4a6b4b7b8ad
    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < 479380acfa63247b5ac62476138f847aefc62692
    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < 4989627157735c1f1619f08e5bc1592418e7c878
    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < d1c946552af299f4fa85bf7da15e328123771128
    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < 196f6c71905aa384c0177acf194a1144d480333b
    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < 8fb11fa4805699c6b73a9c8a9d45807f9874abe3
    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < e9e33faea104381bac80ac79328f0540fc2969f2
    • affected 7f47c7189b3e8f19a589f77a3ad169d7b691b582 – < e82e47584847129a20b8c9f4a1dcde09374fb0e0
  • Linux · Linux

    • affected 3.5
    • unaffected < 3.5
    • unaffected 4.14.322 – ≤ 4.14.*
    • unaffected 4.19.291 – ≤ 4.19.*
    • unaffected 5.4.251 – ≤ 5.4.*
    • unaffected 5.10.188 – ≤ 5.10.*
    • unaffected 5.15.121 – ≤ 5.15.*
    • unaffected 6.1.39 – ≤ 6.1.*
    • unaffected 6.4.4 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .