CVE-2023-54232
published 2025-12-30CVE-2023-54232: 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…
PriorityP421
EPSS
0.18%
8.2th percentile
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.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.25-1 (bookworm) | linux 6.1.25-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < 1a6059f5ed57f48edfe7159404ff7d538d9d405b | 1a6059f5ed57f48edfe7159404ff7d538d9d405b |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < f55cb52ec98b22125f5bda36391edb8894f7e8cf | f55cb52ec98b22125f5bda36391edb8894f7e8cf |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < 2100e374251a8fc00cce1916cfc50f3cb652cbe3 | 2100e374251a8fc00cce1916cfc50f3cb652cbe3 |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8 | df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8 |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < 8bf8d5dade4c5e1d8a2386f29253ed28b5d87735 | 8bf8d5dade4c5e1d8a2386f29253ed28b5d87735 |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < 54fa25ffab2b700df5abd58c136d64a912c53953 | 54fa25ffab2b700df5abd58c136d64a912c53953 |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < ec15405b80fc15ffc87a23d01378ae061c1aba07 | ec15405b80fc15ffc87a23d01378ae061c1aba07 |
| linux | linux | >= f2325ecebc5b7988fd49968bd3a660fd1594dc84 < e36a82bebbf7da814530d5a179bef9df5934b717 | e36a82bebbf7da814530d5a179bef9df5934b717 |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 2.6.18 < 4.14.312 | 4.14.312 |
| linux | linux_kernel | >= 4.15.0 < 4.19.280 | 4.19.280 |
| linux | linux_kernel | >= 4.20.0 < 5.4.240 | 5.4.240 |
| linux | linux_kernel | >= 5.11.0 < 5.15.105 | 5.15.105 |
| linux | linux_kernel | >= 5.16.0 < 6.1.22 | 6.1.22 |
| linux | linux_kernel | >= 5.5.0 < 5.10.177 | 5.10.177 |
| linux | linux_kernel | >= 6.2.0 < 6.2.9 | 6.2.9 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 6.2.8 __get_kernel_nofault null pointer dereference (Nessus ID 281716 / WID-SEC-2025-2941)
vuldb·2026-04-27
CVE-2023-54232 [CRITICAL] Linux Kernel up to 6.2.8 __get_kernel_nofault null pointer dereference (Nessus ID 281716 / WID-SEC-2025-2941)
A vulnerability labeled as critical has been found in Linux Kernel up to 6.2.8. This issue affects the function __get_kernel_nofault. Such manipulation leads to null pointer dereference.
This vulnerability is documented as CVE-2023-54232. The attack requires being on the local network. There is not any exploit available.
The affected component should be upgraded.
GHSA
GHSA-gvjr-wrwm-xp44: 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
ghsa_unreviewed·2025-12-30
CVE-2023-54232 GHSA-gvjr-wrwm-xp44: 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
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 co
OSV
CVE-2023-54232: 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()
osv·2025-12-30
CVE-2023-54232 CVE-2023-54232: 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()
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 contras
OSV
m68k: Only force 030 bus error if PC not in exception table
osv·2025-12-30
CVE-2023-54232 m68k: Only force 030 bus error if PC not in exception table
m68k: Only force 030 bus error if PC not in exception table
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
Red Hat
kernel: m68k: Only force 030 bus error if PC not in exception table
vendor_redhat·2025-12-30
CVE-2023-54232 kernel: m68k: Only force 030 bus error if PC not in exception table
kernel: m68k: Only force 030 bus error if PC not in exception table
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 g
Debian
CVE-2023-54232: linux - In the Linux kernel, the following vulnerability has been resolved: m68k: Only ...
vendor_debian·2023
CVE-2023-54232 CVE-2023-54232: linux - In the Linux kernel, the following vulnerability has been resolved: m68k: Only ...
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 contras
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2023-54232 kernel: m68k: Only force 030 bus error if PC not in exception table
bugzilla·2025-12-30
CVE-2023-54232 CVE-2023-54232 kernel: m68k: Only force 030 bus error if PC not in exception table
CVE-2023-54232 kernel: m68k: Only force 030 bus error if PC not in exception table
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_
Wiz
CVE-2023-54232 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-54232 CVE-2023-54232 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-54232 :
Linux Debian vulnerability analysis and mitigation
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()
https://git.kernel.org/stable/c/1a6059f5ed57f48edfe7159404ff7d538d9d405bhttps://git.kernel.org/stable/c/2100e374251a8fc00cce1916cfc50f3cb652cbe3https://git.kernel.org/stable/c/54fa25ffab2b700df5abd58c136d64a912c53953https://git.kernel.org/stable/c/8bf8d5dade4c5e1d8a2386f29253ed28b5d87735https://git.kernel.org/stable/c/df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8https://git.kernel.org/stable/c/e36a82bebbf7da814530d5a179bef9df5934b717https://git.kernel.org/stable/c/ec15405b80fc15ffc87a23d01378ae061c1aba07https://git.kernel.org/stable/c/f55cb52ec98b22125f5bda36391edb8894f7e8cf
2025-12-30
Published