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.
- Published
- Dec 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.25-1 | 6.1.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1a6059f5ed57f48edfe7159404ff7d538d9d405b | Vendor (CNA) |
| Linux Linux | 2100e374251a8fc00cce1916cfc50f3cb652cbe3 | Vendor (CNA) |
| Linux Linux | 54fa25ffab2b700df5abd58c136d64a912c53953 | Vendor (CNA) |
| Linux Linux | 8bf8d5dade4c5e1d8a2386f29253ed28b5d87735 | Vendor (CNA) |
| Linux Linux | df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8 | Vendor (CNA) |
| Linux Linux | e36a82bebbf7da814530d5a179bef9df5934b717 | Vendor (CNA) |
| Linux Linux | ec15405b80fc15ffc87a23d01378ae061c1aba07 | Vendor (CNA) |
| Linux Linux | f55cb52ec98b22125f5bda36391edb8894f7e8cf | Vendor (CNA) |
| debian:linux | 6.1.25-1 · Debian:12 | Package 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.
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 researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/1a6059f5ed57f48edfe7159404ff7d538d9d405b
- git.kernel.org/stable/c/2100e374251a8fc00cce1916cfc50f3cb652cbe3
- git.kernel.org/stable/c/54fa25ffab2b700df5abd58c136d64a912c53953
- git.kernel.org/stable/c/8bf8d5dade4c5e1d8a2386f29253ed28b5d87735
- git.kernel.org/stable/c/df1da53a7e98f0b2a0eb2241c154f148f2f2c1d8
- git.kernel.org/stable/c/e36a82bebbf7da814530d5a179bef9df5934b717
- git.kernel.org/stable/c/ec15405b80fc15ffc87a23d01378ae061c1aba07
- git.kernel.org/stable/c/f55cb52ec98b22125f5bda36391edb8894f7e8cf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.