CVE-2026-63860: RDMA/core: Prefer NLA_NUL_STRING
In the Linux kernel, the following vulnerability has been resolved:
RDMA/core: Prefer NLANULSTRING
These attributes are evaluated as c-string (passed to strcmp), but NLASTRING doesn't check for the presence of a \0 terminator.
Either this needs to switch to nlastrcmp() and needs to adjust printf fmt specifier to not use plain %s, or this needs to use NLANULSTRING.
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 NLANULSTRING use is the simpler solution.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In Linux kernel RDMA/core, use NLA_NUL_STRING for attributes evaluated as C strings so the terminating NUL is enforced; alternatively, use nla_strcmp() and adjust the printf format specifier instead of plain %s.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63860?
CVE-2026-63860 has a severity rating of high, with a score of 8.4.
How do I fix CVE-2026-63860?
To fix CVE-2026-63860, update the Linux kernel to the latest version where the vulnerability has been addressed.
What component of the Linux kernel is affected by CVE-2026-63860?
CVE-2026-63860 affects the RDMA/core component of the Linux kernel.
What kind of attacks can exploit CVE-2026-63860?
CVE-2026-63860 could potentially allow attackers to cause information disclosure or system crashes due to improper string handling.
Is CVE-2026-63860 a remote vulnerability?
CVE-2026-63860 is considered to have a low attack vector since it requires local access to exploit.