CVE-2026-98429: RDMA/efa: Keep EQ resources alive while IRQ is registered
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 38871ff47e2a02f8d9a333a65f358d987247b5b0, 3cd652dfcd822af26ba75d6d2d245ea7f73b499e, 795eb34bfd8b1ab347adc41a11e4bb97c3ac0ce6; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 38871ff47e2a02f8d9a333a65f358d987247b5b0, 3cd652dfcd822af26ba75d6d2d245ea7f73b499e, 795eb34bfd8b1ab347adc41a11e4bb97c3ac0ce6; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 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: RDMA/efa: Keep EQ resources alive while IRQ is registered The completion IRQ handler accesses the EQ state and DMA buffer. Its IRQ was registered before that state was initialized, while teardown released the buffer before free_irq() synchronized the handler. Initialize the EQ without arming it, register the IRQ, and then arm it. Reverse the resource order during teardown by freeing the IRQ before destroying the EQ.
- Published
- Oct 14, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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
- 5.16affected
- 2a152512a155aaf27c3e67834ffafaed9525a7b5 and later · before 3cd652dfcd822af26ba75d6d2d245ea7f73b499eaffected · git
- 2a152512a155aaf27c3e67834ffafaed9525a7b5 and later · before c767e2812cac83fef70fb8932c3f0fe97dff9388affected · git
- 2a152512a155aaf27c3e67834ffafaed9525a7b5 and later · before 795eb34bfd8b1ab347adc41a11e4bb97c3ac0ce6affected · git
- 2a152512a155aaf27c3e67834ffafaed9525a7b5 and later · before 38871ff47e2a02f8d9a333a65f358d987247b5b0affected · git
- 2a152512a155aaf27c3e67834ffafaed9525a7b5 and later · before 9ecd3dcbdf1f315aadc049b291f59c79dc478062affected · git
- 2a152512a155aaf27c3e67834ffafaed9525a7b5 and later · before e22a3627b7151754f07f90ea3d1ab6e85f5d93f4affected · git
- before 5.16not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-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
Published before and after this one in the same product
- ← EarlierCVE-2026-98427Oct 14, 2026 · net/sched: codel: bound the dropping loop per dequeue call0Monitor
- ← EarlierCVE-2026-98428Oct 14, 2026 · ALSA: usb: 6fire: Avoid embedded URBs0Monitor
- Later →CVE-2026-98430Oct 14, 2026 · RDMA/efa: Keep admin queues alive while IRQ is registered0Monitor
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 | 38871ff47e2a02f8d9a333a65f358d987247b5b0 | Vendor (CNA) |
| Linux Linux | 3cd652dfcd822af26ba75d6d2d245ea7f73b499e | Vendor (CNA) |
| Linux Linux | 795eb34bfd8b1ab347adc41a11e4bb97c3ac0ce6 | Vendor (CNA) |
| Linux Linux | 9ecd3dcbdf1f315aadc049b291f59c79dc478062 | Vendor (CNA) |
| Linux Linux | c767e2812cac83fef70fb8932c3f0fe97dff9388 | Vendor (CNA) |
| Linux Linux | e22a3627b7151754f07f90ea3d1ab6e85f5d93f4 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-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.
- Published
- Fix recordedsame day
- TodayOct 30, 2026+16 d
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-1334 · Oct 15, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3cd652dfcd822af26ba75d6d2d245ea7f73b499e
- git.kernel.org/stable/c/795eb34bfd8b1ab347adc41a11e4bb97c3ac0ce6
- git.kernel.org/stable/c/9ecd3dcbdf1f315aadc049b291f59c79dc478062
- git.kernel.org/stable/c/c767e2812cac83fef70fb8932c3f0fe97dff9388
- git.kernel.org/stable/c/e22a3627b7151754f07f90ea3d1ab6e85f5d93f4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.