openrisc: fix arbitrary kernel memory access via or1k_atomic syscall
Noroxi assessment
Priority: Monitor (action score 31/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.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1f2e92e499d863f81df1732af59b4a3559969193, 497cba0b02e5555d99fe9ee1dc478af743ab7f7a, 574ae2ac2b314aa33498cd2c28add106cbe644f2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1f2e92e499d863f81df1732af59b4a3559969193, 497cba0b02e5555d99fe9ee1dc478af743ab7f7a, 574ae2ac2b314aa33498cd2c28add106cbe644f2 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: openrisc: fix arbitrary kernel memory access via or1k_atomic syscall sys_or1k_atomic() (syscall 244 in the "or1k" ABI) takes two user pointers, v1 and v2, and swaps the words they point to in hand-written assembly. l.lwz r29,0(r4) l.lwz r27,0(r5) l.sw 0(r4),r27 l.sw 0(r5),r29 The pointers are not checked with access_ok(). The four memory accesses also have no exception table entries. A caller passes a kernel address as either pointer, and the syscall reads from and writes to it directly. This gives an unprivileged process a kernel read/write primitive. It overwrites kernel data such as the sys_call_table, gaining code execution in kernel context. Check both pointers before entering the critical section. Add fixups for the four memory accesses so faults on valid but unmapped user addresses return -EFAULT. [shorne@gmail.com: fix comment style]
- Published
- Sep 11, 2026
- Updated
- Sep 14, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 3.1affected
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before bf310718c6fa6adeee06d207a55489546d860e2caffected · git
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before 497cba0b02e5555d99fe9ee1dc478af743ab7f7aaffected · git
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before 1f2e92e499d863f81df1732af59b4a3559969193affected · git
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before 574ae2ac2b314aa33498cd2c28add106cbe644f2affected · git
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before a520e8cac54fb403f3800125b606f55fcad42cb9affected · git
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before d64a75369cd0f2ee79afcc9d9ca34a3890989379affected · git
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before b53435c079c78f89f70a62dd5a322cca4e292b34affected · git
- 9d02a4283e9ce4e9ca11ff00615bdacdb0515a1a and later · before 78004e9a87f240df03e2f73120d291763c32e0a7affected · git
- before 3.1not 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 | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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 | 1f2e92e499d863f81df1732af59b4a3559969193 | Vendor (CNA) |
| Linux Linux | 497cba0b02e5555d99fe9ee1dc478af743ab7f7a | Vendor (CNA) |
| Linux Linux | 574ae2ac2b314aa33498cd2c28add106cbe644f2 | Vendor (CNA) |
| Linux Linux | 78004e9a87f240df03e2f73120d291763c32e0a7 | Vendor (CNA) |
| Linux Linux | a520e8cac54fb403f3800125b606f55fcad42cb9 | Vendor (CNA) |
| Linux Linux | b53435c079c78f89f70a62dd5a322cca4e292b34 | Vendor (CNA) |
| Linux Linux | bf310718c6fa6adeee06d207a55489546d860e2c | Vendor (CNA) |
| Linux Linux | d64a75369cd0f2ee79afcc9d9ca34a3890989379 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
Show all references (7 more)Show less
- git.kernel.org/stable/c/497cba0b02e5555d99fe9ee1dc478af743ab7f7a
- git.kernel.org/stable/c/574ae2ac2b314aa33498cd2c28add106cbe644f2
- git.kernel.org/stable/c/78004e9a87f240df03e2f73120d291763c32e0a7
- git.kernel.org/stable/c/a520e8cac54fb403f3800125b606f55fcad42cb9
- git.kernel.org/stable/c/b53435c079c78f89f70a62dd5a322cca4e292b34
- git.kernel.org/stable/c/bf310718c6fa6adeee06d207a55489546d860e2c
- git.kernel.org/stable/c/d64a75369cd0f2ee79afcc9d9ca34a3890989379
Vendor advisories and official records. Exploit/PoC links are deliberately left out.