Skip to main content

In the Linux kernel, the following vulnerability has been resolved: rust: irq: pass RegistrationInner as cookie to request_irq With commit… (CVE-2026-98938)

0
Medium
Published: 10/23/2026 (10/23/2026, 15:31:31 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's Rust IRQ handling was resolved by changing how RegistrationInner is passed as a cookie to request_irq. The issue involved accessing uninitialized memory in the IRQ callback due to the IRQ being enabled before RegistrationInner was fully initialized. This flaw was fixed by ensuring RegistrationInner's fields are initialized before passing it as the IRQ cookie. The vulnerability does not affect mainline Linux kernels where a related commit removed the problematic pattern.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/23/2026, 19:01:36 UTC

Technical Analysis

The vulnerability in the Linux kernel's Rust IRQ subsystem arose because Devres::new() was changed to return a Result<Self> by value rather than initializing in-place. Since request_irq() was called inside Devres::new(), the registration.inner structure was uninitialized when the IRQ was enabled. Consequently, the IRQ callback could access uninitialized memory via registration.inner.device(). The fix involved storing the Device and handler pointer inside RegistrationInner and passing RegistrationInner as the IRQ cookie only after its fields were fully initialized. This issue is not present in mainline kernels due to a prior commit that removed Devres from irq::Registration and reordered request_irq() after initialization.

Potential Impact

The vulnerability could lead to the IRQ callback reading uninitialized memory, which may cause undefined behavior or system instability. There is no information about exploitation in the wild or direct security impact such as privilege escalation or denial of service.

Mitigation Recommendations

A fix is available and has been applied in the Linux kernel by ensuring RegistrationInner is fully initialized before being passed to request_irq. Users should update to the patched kernel versions containing commit ba268514ea14 or later. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-4546-wrv4-93xw
Osv Schema Version
1.4.0
Aliases
["CVE-2026-98938"]

Threat ID: 6adbaad0d73cc49347b205a8

Added to database: 10/23/2026, 18:43:28 UTC

Last enriched: 10/23/2026, 19:01:36 UTC

Last updated: 10/23/2026, 21:25:06 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses