CVE-2023-54232
Vulnerability Scoring
Analysis In Progress
CVE-2023-54232 Vulnerability Analysis & Exploit Details
CVE-2023-54232
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2023-54232 Details
Status: Awaiting Analysis
Last updated: 🕣 31 Dec 2025, 20:42 UTC
Originally published on: 🕐 30 Dec 2025, 13:16 UTC
Time between publication and last update: 1 days
CVSS Release:
CVE-2023-54232 Vulnerability Summary
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() 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.
Assessing the Risk of CVE-2023-54232
Access Complexity Graph
The exploitability of CVE-2023-54232 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2023-54232
No exploitability data is available for CVE-2023-54232.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2023-54232, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2023-54232, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2023-54232 does not compromise confidentiality.
-
Integrity:
None
CVE-2023-54232 does not impact data integrity.
-
Availability:
None
CVE-2023-54232 does not affect system availability.
CVE-2023-54232 References
External References
- https://git.kernel.org/stable/c/1a6059f5ed57f48edfe7159404ff7d538d9d405b
- https://git.kernel.org/stable/c/2100e374251a8fc00cce1916cfc50f3cb652cbe3
- https://git.kernel.org/stable/c/54fa25ffab2b700df5abd58c136d64a912c53953
- https://git.kernel.org/stable/c/8bf8d5dade4c5e1d8a2386f29253ed28b5d87735
- https://git.kernel.org/stable/c/df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8
- https://git.kernel.org/stable/c/e36a82bebbf7da814530d5a179bef9df5934b717
- https://git.kernel.org/stable/c/ec15405b80fc15ffc87a23d01378ae061c1aba07
- https://git.kernel.org/stable/c/f55cb52ec98b22125f5bda36391edb8894f7e8cf
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2023-54232: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2026-1251 – The SupportCandy – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions...
- CVE-2026-0683 – The SupportCandy – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to SQL Injection via the Number-type custom field f...
- CVE-2026-1431 – The Booking Calendar plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the wpbc_ajax_WPBC_FLEX...
- CVE-2025-15525 – The Ajax Load More – Infinite Scroll, Load More, & Lazy Load plugin for WordPress is vulnerable to unauthorized access of data due to incorrect aut...
- CVE-2025-15510 – The NEX-Forms – Ultimate Forms Plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the NF5_Expor...