# CVE-2026-92517: bpf, riscv: Fix extable handling for arena load_acquire

> A local attacker can leak stale register data via BPF arena load_acquire faults or cause a kernel oops due to missing exception handling in the RISC-V Linux kernel.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-92517, DEBIAN-CVE-2026-92517, GHSA-92r6-5jjc-jv43, UBUNTU-CVE-2026-92517

## What is CVE-2026-92517?

CVE-2026-92517 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

bpf, riscv: Fix extable handling for arena load_acquire

emit_atomic_ld_st() returns 1 to have build_body() skip the zext after
a sub-word load_acquire. The caller does "ret = ret ?:
add_exception_handler(...)", which skips add_exception_handler() on any
non-zero ret, so the extable entry is missing and a faulting
PROBE_ATOMIC load_acquire oopses.

REG_DONT_CLEAR_MARKER leaves rd stale on fault, and the verifier still
thinks the load overwrote it, so a program can leak it through a map.

Check ret >= 0 before calling add_exception_handler(), and pass rd for
LOAD_ACQ so the fault zeroes rd like a PROBE_MEM load. Return ret
unchanged for the zext skip.

## Which versions are affected by CVE-2026-92517?


## How do I fix CVE-2026-92517?

Apply the vendor's patch.

## Is CVE-2026-92517 being exploited?

There is no known exploitation of CVE-2026-92517 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92517 and fix it if it is affected.

What it is: CVE-2026-92517 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92517 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92517/ (Markdown: https://insights.sbomify.com/CVE-2026-92517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92517
- OSV: https://osv.dev/vulnerability/CVE-2026-92517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92517/
Summaries are generated and may contain mistakes; the official description above is the record.