CVE-2023-54232 — 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 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < 1a6059f5ed57f48edfe7159404ff7d538d9d405b≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < f55cb52ec98b22125f5bda36391edb8894f7e8cf≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < 2100e374251a8fc00cce1916cfc50f3cb652cbe3≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < 8bf8d5dade4c5e1d8a2386f29253ed28b5d87735≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < 54fa25ffab2b700df5abd58c136d64a912c53953≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < ec15405b80fc15ffc87a23d01378ae061c1aba07≥ f2325ecebc5b7988fd49968bd3a660fd1594dc84 and < e36a82bebbf7da814530d5a179bef9df5934b717 and 1 moreversion 2.6.18 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/2100e374251a8fc00cce1916cfc50f3cb652cbe3
- git.kernel.org/stable/c/df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8
- git.kernel.org/stable/c/e36a82bebbf7da814530d5a179bef9df5934b717
- git.kernel.org/stable/c/54fa25ffab2b700df5abd58c136d64a912c53953
- git.kernel.org/stable/c/ec15405b80fc15ffc87a23d01378ae061c1aba07
- git.kernel.org/stable/c/1a6059f5ed57f48edfe7159404ff7d538d9d405b
- git.kernel.org/stable/c/f55cb52ec98b22125f5bda36391edb8894f7e8cf
- git.kernel.org/stable/c/8bf8d5dade4c5e1d8a2386f29253ed28b5d87735
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 7h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 7h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-54232 is "m68k: Only force 030 bus error if PC not in exception table", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.