Dismissed
(max. allowed matches exceeded)
Permalink
CVE-2026-63860
8.4 HIGH
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Local (L)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): None (N)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Local (L)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): None (N)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
RDMA/core: Prefer NLA_NUL_STRING
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
Affected products
Linux
- <137b5918931d4d05aa8ea8d3adf67f7224eef63c
- <c26a0052cceed4c4d380ee5808b699f937fb58d8
- =<6.18.*
- <3.16
- =<7.0.*
- <f2c7b39dde2e61df8157066969cc2a408cd3dcd9
- =<6.12.*
- <5877c043398d5fa0e93919a3d837e5cd7a98a961
- <6ed3d14fc45d3da6025e7fe4a6a09066856698e2
- <87111356d58d86edb221ba144d261ed83a5b8bbe
- =<6.1.*
- =<*
- =<6.6.*
- <fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf
- ==3.16
- =<5.15.*
- <abda65bdd13084c771842adaac1f652d0660dd82
- =<5.10.*