CVE-2023-54232 Details
Description
In the Linux kernel, the following vulnerability has been resolved: m68k: Only force 030 bus error if PC not in exception table __get_kernel_nofault() does copy data in supervisor mode when forcing a task backtrace log through /proc/sysrq_trigger. This is expected cause a bus error exception on e.g. NULL pointer dereferencing when logging a kernel task has no workqueue associated. This bus error ought to be ignored. Our 030 bus error handler is ill equipped to deal with this: Whenever ssw indicates a kernel mode access on a data fault, we don't even attempt to handle the fault and instead always send a SEGV signal (or panic). As a result, the check for exception handling at the fault PC (buried in send_sig_fault() which gets called from do_page_fault() eventually) is never used. In contrast, both 040 and 060 access error handlers do not care whether a fault happened on supervisor mode access, and will call do_page_fault() on those, ultimately honoring the exception table. Add a check in bus_error030 to call do_page_fault() in case we do have an entry for the fault PC in our exception table. I had attempted a fix for this earlier in 2019 that did rely on testing pagefault_disabled() (see link below) to achieve the same thing, but this patch should be more generic. Tested on 030 Atari Falcon.
A vulnerability exists in the Linux kernel m68k architecture related to how bus errors are handled, particularly for the 030 variant. The issue arises when the kernel task backtrace is logged via the /proc/sysrq_trigger, which can inadvertently cause a bus error by dereferencing a NULL pointer, especially when no workqueue is associated with the task. The current bus error handler for the 030 variant is not properly equipped to manage this situation. Instead of addressing the fault, it defaults to sending a segmentation fault signal or panicking, thereby bypassing the exception handling mechanism that could mitigate the issue. This vulnerability affects several versions of the Linux kernel m68k architecture.
Users can update to the latest version of the Linux kernel where this vulnerability has been addressed. The specific commit that resolves this issue is available in the Linux kernel stable tree.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 30, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1a6059f5ed57f48edfe7159404ff7d538d9d405b | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/2100e374251a8fc00cce1916cfc50f3cb652cbe3 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/54fa25ffab2b700df5abd58c136d64a912c53953 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/8bf8d5dade4c5e1d8a2386f29253ed28b5d87735 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/e36a82bebbf7da814530d5a179bef9df5934b717 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/ec15405b80fc15ffc87a23d01378ae061c1aba07 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/f55cb52ec98b22125f5bda36391edb8894f7e8cf | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 28, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 30, 2025 | New CVE Received | kernel.org |
Volerion