CVE-2023-54255
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Incorrect DMA channel offset calculation in the Linux kernel's SH DMA driver causes kernel panics on SH3/SH4/SH4A SoCs.
The Linux kernel's SH DMA driver contains a flaw in its channel offset calculation for various SH3, SH4, and SH4A family SoCs. These SoCs can have a varying number of DMA channels distributed across up to two DMAC modules. The existing implementation fails to accommodate these variations, leading to wrong channel offset calculations [1].
The vulnerability manifests when the driver computes base addresses for DMA channels. The incorrect offset can cause out-of-bounds access or misaligned register writes, potentially leading to a kernel panic. An attacker with local access to trigger DMA operations could exploit this bug [2].
The impact is a denial of service via kernel panic. Given that the SH architecture is primarily used in embedded systems, physical or local access is typically required. The vulnerability does not appear to allow privilege escalation beyond crashing the system.
Patches have been applied to the Linux kernel stable tree, correcting the dma_base_addr() function and the dmaor_read_reg()/dmaor_write_reg() functions to select the correct DMAC module base. Users should update to the latest stable kernel version containing these fixes [3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
8bca700b48c72479380acfa63498962715773d1c946552af2196f6c71905a8fb11fa48056e9e33faea104e82e47584847Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/196f6c71905aa384c0177acf194a1144d480333bnvd
- git.kernel.org/stable/c/479380acfa63247b5ac62476138f847aefc62692nvd
- git.kernel.org/stable/c/4989627157735c1f1619f08e5bc1592418e7c878nvd
- git.kernel.org/stable/c/8fb11fa4805699c6b73a9c8a9d45807f9874abe3nvd
- git.kernel.org/stable/c/bca700b48c72f4ffeee977a2ed0eb4a6b4b7b8adnvd
- git.kernel.org/stable/c/d1c946552af299f4fa85bf7da15e328123771128nvd
- git.kernel.org/stable/c/e82e47584847129a20b8c9f4a1dcde09374fb0e0nvd
- git.kernel.org/stable/c/e9e33faea104381bac80ac79328f0540fc2969f2nvd
News mentions
0No linked articles in our index yet.