RDMA/core: Prefer NLA_NUL_STRING
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.4epss 0.1%
exploitation probability
0.1%top 97% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/137b5918931d4d05aa8ea8d3adf67f7224eef63chttps://git.kernel.org/stable/c/5877c043398d5fa0e93919a3d837e5cd7a98a961https://git.kernel.org/stable/c/6ed3d14fc45d3da6025e7fe4a6a09066856698e2https://git.kernel.org/stable/c/87111356d58d86edb221ba144d261ed83a5b8bbehttps://git.kernel.org/stable/c/abda65bdd13084c771842adaac1f652d0660dd82https://git.kernel.org/stable/c/c26a0052cceed4c4d380ee5808b699f937fb58d8https://git.kernel.org/stable/c/f2c7b39dde2e61df8157066969cc2a408cd3dcd9https://git.kernel.org/stable/c/fcd07d3b8ee7a39b344d73aed69c1a68cd9eacdf