Skip to main content
VulnerabilityPublished Updated

CVE-2026-63860: Linux kernel · RDMA/core: Prefer NLA_NUL_STRING

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High · fixed in fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf, f2c7b39dde2e61df8157066969cc2a408cd3dcd9, c26a0052cceed4c4d380ee5808b699f937fb58d8 +5
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf
Fixed in
  • fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf
LinuxLinuxAffected
  • ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < f2c7b39dde2e61df8157066969cc2a408cd3dcd9
Fixed in
  • f2c7b39dde2e61df8157066969cc2a408cd3dcd9
LinuxLinuxAffected
  • ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < c26a0052cceed4c4d380ee5808b699f937fb58d8
Fixed in
  • c26a0052cceed4c4d380ee5808b699f937fb58d8
LinuxLinuxAffected
  • ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < abda65bdd13084c771842adaac1f652d0660dd82
Fixed in
  • abda65bdd13084c771842adaac1f652d0660dd82
LinuxLinuxAffected
  • ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < 87111356d58d86edb221ba144d261ed83a5b8bbe
Fixed in
  • 87111356d58d86edb221ba144d261ed83a5b8bbe
LinuxLinuxAffected
  • ≥ 30dc5e63d6a5ad24894b5512d10b228d73645a44, < 5877c043398d5fa0e93919a3d837e5cd7a98a961
Fixed in
  • 5877c043398d5fa0e93919a3d837e5cd7a98a961

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Prefer NLA_NUL_STRING These attributes are evaluated as c-string (passed to strcmp), but NLA_STRING doesn't check for the presence of a \0 terminator. Either this needs to switch to nla_strcmp() and needs to adjust printf fmt specifier to not use plain %s, or this needs to use NLA_NUL_STRING. As the code has been this way for long time, it seems to me that userspace does include the terminating nul, even tough its not enforced so far, and thus NLA_NUL_STRING use is the simpler solution.

References

Community reviews

Loading reviews…