Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-93110: RDMA/core: Wait for RCU callbacks before unloading ib_core

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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 0d5817fa4819abdc445fa77b5be4f0d49334a864, 1646e123e56c3ad679fbfb571e8eef6386efb729, 48b72fa0d209a92fb51b834a6080171cfa207b2c.

Low priority for now. Upgrade to Linux Linux 0d5817fa4819abdc445fa77b5be4f0d49334a864, 1646e123e56c3ad679fbfb571e8eef6386efb729, 48b72fa0d209a92fb51b834a6080171cfa207b2c 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/core: Wait for RCU callbacks before unloading ib_core put_gid_ndev() is queued with call_rcu() and implemented in ib_core. Stopping the workqueues does not drain callbacks already queued, so RCU could invoke it after the module code has been unloaded. synchronize_rcu() does not wait for callbacks. Wait for them after all producers have stopped.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Follow CVE-2026-93110

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

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 help

Affected 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.2affected
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 82dfd1df456227279b1c8c648983a530f2612098affected · git
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 1646e123e56c3ad679fbfb571e8eef6386efb729affected · git
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 8e4f1677c09d75d738099f42afcf65d8587b664aaffected · git
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 7853af5f15738dc00aebaa1fc9f1f0df40f6f603affected · git
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 0d5817fa4819abdc445fa77b5be4f0d49334a864affected · git
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 9d998297fdaf47492f6679287f6552879d1a7e3aaffected · git
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 48b72fa0d209a92fb51b834a6080171cfa207b2caffected · git
    • 943bd984b108b3bb778790c2da4ae8d186b547e6 and later · before 7d75592114d1664623c8cf191a12b38052c04483affected · git
    • before 5.2not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93108Sep 17, 2026 · RDMA/ipoib: Drain RCU callbacks during module teardown
    0Monitor
  • ← EarlierCVE-2026-93109Sep 17, 2026 · RDMA/mlx5: Drain RCU callbacks during module teardown
    0Monitor
  • Later →CVE-2026-93111Sep 17, 2026 · bpf: Mark tracing_multi trampolines as ftrace managed
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0d5817fa4819abdc445fa77b5be4f0d49334a864Vendor (CNA)
Linux Linux1646e123e56c3ad679fbfb571e8eef6386efb729Vendor (CNA)
Linux Linux48b72fa0d209a92fb51b834a6080171cfa207b2cVendor (CNA)
Linux Linux7853af5f15738dc00aebaa1fc9f1f0df40f6f603Vendor (CNA)
Linux Linux7d75592114d1664623c8cf191a12b38052c04483Vendor (CNA)
Linux Linux82dfd1df456227279b1c8c648983a530f2612098Vendor (CNA)
Linux Linux8e4f1677c09d75d738099f42afcf65d8587b664aVendor (CNA)
Linux Linux9d998297fdaf47492f6679287f6552879d1a7e3aVendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

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.

Finders, 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).

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records