Skip to content
Noroxi
CVE-2023-54232· NVD / CVE Program· CNA Linux

m68k: Only force 030 bus error if PC not in exception table

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 1a6059f5ed57f48edfe7159404ff7d538d9d405b, 2100e374251a8fc00cce1916cfc50f3cb652cbe3, 54fa25ffab2b700df5abd58c136d64a912c53953.

Low priority for now. Upgrade to Linux Linux 1a6059f5ed57f48edfe7159404ff7d538d9d405b, 2100e374251a8fc00cce1916cfc50f3cb652cbe3, 54fa25ffab2b700df5abd58c136d64a912c53953 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-54232

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.18affected
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before 1a6059f5ed57f48edfe7159404ff7d538d9d405baffected · git
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before f55cb52ec98b22125f5bda36391edb8894f7e8cfaffected · git
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before 2100e374251a8fc00cce1916cfc50f3cb652cbe3affected · git
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8affected · git
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before 8bf8d5dade4c5e1d8a2386f29253ed28b5d87735affected · git
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before 54fa25ffab2b700df5abd58c136d64a912c53953affected · git
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before ec15405b80fc15ffc87a23d01378ae061c1aba07affected · git
    • f2325ecebc5b7988fd49968bd3a660fd1594dc84 and later · before e36a82bebbf7da814530d5a179bef9df5934b717affected · git
    • before 2.6.18not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.25-16.1.25-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54230Dec 30, 2025 · amba: bus: fix refcount leak
    0Monitor
  • ← EarlierCVE-2023-54231Dec 30, 2025 · net: libwx: fix memory leak in wx_setup_rx_resources
    0Monitor
  • Later →CVE-2023-54235Dec 30, 2025 · PCI/DOE: Fix destroy_work_on_stack() race
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1a6059f5ed57f48edfe7159404ff7d538d9d405bVendor (CNA)
Linux Linux2100e374251a8fc00cce1916cfc50f3cb652cbe3Vendor (CNA)
Linux Linux54fa25ffab2b700df5abd58c136d64a912c53953Vendor (CNA)
Linux Linux8bf8d5dade4c5e1d8a2386f29253ed28b5d87735Vendor (CNA)
Linux Linuxdf1da53a7e98f0b2a0eb2241c154f148f2f2c1d8Vendor (CNA)
Linux Linuxe36a82bebbf7da814530d5a179bef9df5934b717Vendor (CNA)
Linux Linuxec15405b80fc15ffc87a23d01378ae061c1aba07Vendor (CNA)
Linux Linuxf55cb52ec98b22125f5bda36391edb8894f7e8cfVendor (CNA)
debian:linux6.1.25-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records