# CVE-2026-98938: rust: irq: pass RegistrationInner as cookie to request_irq


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-98938, DEBIAN-CVE-2026-98938, GHSA-4546-wrv4-93xw, UBUNTU-CVE-2026-98938

## What is CVE-2026-98938?

CVE-2026-98938 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

rust: irq: pass RegistrationInner as cookie to request_irq

With commit ba268514ea14 ("rust: devres: fix race condition due to
nesting"), Devres::new() returns Result<Self> by value instead of
initializing in-place via PinInit. Because request_irq() is called
inside Devres::new(), registration.inner is still uninitialized when the
IRQ is enabled, so accessing registration.inner.device() in the IRQ
callback can read uninitialized memory.

Fix this by storing the Device and handler pointer in RegistrationInner
and passing RegistrationInner as the IRQ cookie after its fields are
initialized.

This is not needed in mainline because commit 98c63ce4d760 ("rust: irq:
make Registration compatible with lifetime-bound drivers") removed
Devres from irq::Registration and moved request_irq() after all fields
are initialized.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98938 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98938 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98938 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-98938/ (Markdown: https://insights.sbomify.com/CVE-2026-98938/index.md)
```

## Sources

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

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