CVE Tools
Track your stack

CVE-2026-98252

RDMA/core: fix refcount bug in iwpm_get_nlmsg_request()

No known exploitation. EPSS puts it in the 2nd percentile. Fixed versions are out.

CVSS 3.17.0HighEPSS percentile2nd0.1% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix1 product4 fixed builds listed below

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < 52c13c63bb3662c108244e7447055e30bf40244eUpgrade to: 52c13c63bb3662c108244e7447055e30bf40244eAffected: ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < 8a91609032d47e77bcb37bc8f6e88d89340d2709Upgrade to: 8a91609032d47e77bcb37bc8f6e88d89340d2709Affected: ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < ce8a379598bd4058081416abea4279fd05a95374Upgrade to: ce8a379598bd4058081416abea4279fd05a95374Affected: ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < 2fbac8a56004b6ce54fbfe845d4b25da6e0b55e8Upgrade to: 2fbac8a56004b6ce54fbfe845d4b25da6e0b55e8 + 4 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

In the Linux kernel, the following vulnerability has been resolved: RDMA/core: fix refcount bug in iwpm_get_nlmsg_request() iwpm_get_nlmsg_request() initializes refcount _after_ list_add_tail() making it accessible to global list where another CPU can kref_get() on nlmsg_request causing a refcount "addition on 0" bug. Fix this by initializing kref _before_ list_add_tail() so refcount for nlmsg_request can be incremented/decremented normally. In addition, also initialize every field before list_add_tail().

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS2nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.1% chance of exploitation activity in the next 30 days, which ranks it in the 2nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

3 events over 1 day, from the signal feeds we watch.

  1. Record updated
  2. Publishedrecord updated

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 7.0 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Sources

References in the record

And 5 more references. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.