bna: ensure the copied buf is NUL terminated
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.3%
exploitation probability
0.3%top 78% of all CVEs
observed exploitation
nono source reports it
In the Linux kernel, the following vulnerability has been resolved:
bna: ensure the copied buf is NUL terminated
Currently, we allocate a nbytes-sized kernel buffer and copy nbytes from
userspace to that buffer. Later, we use sscanf on this buffer but we don't
ensure that the string is terminated inside the buffer, this can lead to
OOB read when using sscanf. Fix this issue by using memdup_user_nul
instead of memdup_user.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/06cb37e2ba6441888f24566a997481d4197b4e32https://git.kernel.org/stable/c/0f560240b4cc25d3de527deb257cdf072c0102a9https://git.kernel.org/stable/c/1518b2b498a0109eb6b15755169d3b6607356b35https://git.kernel.org/stable/c/6f0f19b79c085cc891c418b768f26f7004bd51a4https://git.kernel.org/stable/c/80578ec10335bc15ac35fd1703c22aab34e39fddhttps://git.kernel.org/stable/c/8c34096c7fdf272fd4c0c37fe411cd2e3ed0ee9fhttps://git.kernel.org/stable/c/bd502ba81cd1d515deddad7dbc6b812b14b97147https://git.kernel.org/stable/c/e19478763154674c084defc62ae0d64d79657f91https://lists.debian.org/debian-lts-announce/2024/06/msg00019.htmlhttps://lists.debian.org/debian-lts-announce/2024/06/msg00020.htmlhttps://security.netapp.com/advisory/ntap-20240912-0007/