m68k: Only force 030 bus error if PC not in exception table
Summary
| CVE | CVE-2023-54232 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-12-30 13:16:11 UTC |
| Updated | 2026-10-28 19:10:00 UTC |
| 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. |
Risk And Classification
EPSS: 0.002110000 probability, percentile 0.113180000 (date 2026-10-29)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 1a6059f5ed57f48edfe7159404ff7d538d9d405b git | Not specified |
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 f55cb52ec98b22125f5bda36391edb8894f7e8cf git | Not specified |
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 2100e374251a8fc00cce1916cfc50f3cb652cbe3 git | Not specified |
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8 git | Not specified |
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 8bf8d5dade4c5e1d8a2386f29253ed28b5d87735 git | Not specified |
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 54fa25ffab2b700df5abd58c136d64a912c53953 git | Not specified |
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 ec15405b80fc15ffc87a23d01378ae061c1aba07 git | Not specified |
| CNA | Linux | Linux | affected f2325ecebc5b7988fd49968bd3a660fd1594dc84 e36a82bebbf7da814530d5a179bef9df5934b717 git | Not specified |
| CNA | Linux | Linux | affected 2.6.18 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.18 semver | Not specified |
| CNA | Linux | Linux | unaffected 4.14.312 4.14.* semver | Not specified |
| CNA | Linux | Linux | unaffected 4.19.280 4.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.4.240 5.4.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.177 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.105 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.22 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.2.9 6.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/8bf8d5dade4c5e1d8a2386f29253ed28b5d87735 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e36a82bebbf7da814530d5a179bef9df5934b717 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2100e374251a8fc00cce1916cfc50f3cb652cbe3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ec15405b80fc15ffc87a23d01378ae061c1aba07 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/1a6059f5ed57f48edfe7159404ff7d538d9d405b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f55cb52ec98b22125f5bda36391edb8894f7e8cf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/54fa25ffab2b700df5abd58c136d64a912c53953 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.