Kernel panic via mishandled 68030 bus fault
Published Dec 30, 2025 · Updated Dec 30, 2025
Denial of service in the Linux kernel m68k bus-error path allows local users to panic an m68030 system through a task backtrace request. The bus_error030 handler treats supervisor-mode data faults as fatal before consulting the exception table, so an expected __get_kernel_nofault error reaches SIGSEGV or panic handling. Reachability requires privileged access to /proc/sysrq_trigger, m68030 hardware, and backtrace logging of a kernel task without an associated workqueue.
Summary
What happened
Denial of service in the Linux kernel m68k bus-error path allows local users to panic an m68030 system through a task backtrace request. The bus_error030 handler treats supervisor-mode data faults as fatal before consulting the exception table, so an expected __get_kernel_nofault error reaches SIGSEGV or panic handling. Reachability requires privileged access to /proc/sysrq_trigger, m68030 hardware, and backtrace logging of a kernel task without an associated workqueue.
The record
- CVE
- CVE-2023-54232
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1a6059f5ed57f48edfe7159404ff7d538d9d405b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2100e374251a8fc00cce1916cfc50f3cb652cbe3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <54fa25ffab2b700df5abd58c136d64a912c53953
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8bf8d5dade4c5e1d8a2386f29253ed28b5d87735
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e36a82bebbf7da814530d5a179bef9df5934b717
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ec15405b80fc15ffc87a23d01378ae061c1aba07
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f55cb52ec98b22125f5bda36391edb8894f7e8cf
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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