Kernel panic via incorrect DMA channel offsets
Published Dec 30, 2025 · Updated Dec 30, 2025
Denial of service in the Linux kernel allows local users to cause a kernel panic through DMA on affected SH-family systems. The dma_base_addr(), dmaor_read_reg(), and dmaor_write_reg() paths miscalculate channel offsets and can select the wrong DMAC module base. Reachability requires an SH3, SH4, or SH4A system using this driver and a channel layout the old calculation mishandles; the bounded consequence is a kernel panic.
Summary
What happened
Denial of service in the Linux kernel allows local users to cause a kernel panic through DMA on affected SH-family systems. The dma_base_addr(), dmaor_read_reg(), and dmaor_write_reg() paths miscalculate channel offsets and can select the wrong DMAC module base. Reachability requires an SH3, SH4, or SH4A system using this driver and a channel layout the old calculation mishandles; the bounded consequence is a kernel panic.
The record
- CVE
- CVE-2023-54255
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.5
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <196f6c71905aa384c0177acf194a1144d480333b
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <479380acfa63247b5ac62476138f847aefc62692
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <4989627157735c1f1619f08e5bc1592418e7c878
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <8fb11fa4805699c6b73a9c8a9d45807f9874abe3
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <bca700b48c72f4ffeee977a2ed0eb4a6b4b7b8ad
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <d1c946552af299f4fa85bf7da15e328123771128
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <e82e47584847129a20b8c9f4a1dcde09374fb0e0
- Affected versionversion=7f47c7189b3e8f19a589f77a3ad169d7b691b582 <e9e33faea104381bac80ac79328f0540fc2969f2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo