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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws-5.15 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-azure | < any | UNKNOWN |
git.kernel.org/linus/8c34096c7fdf272fd4c0c37fe411cd2e3ed0ee9f (6.9-rc7)
git.kernel.org/stable/c/06cb37e2ba6441888f24566a997481d4197b4e32
git.kernel.org/stable/c/0f560240b4cc25d3de527deb257cdf072c0102a9
git.kernel.org/stable/c/1518b2b498a0109eb6b15755169d3b6607356b35
git.kernel.org/stable/c/6f0f19b79c085cc891c418b768f26f7004bd51a4
git.kernel.org/stable/c/80578ec10335bc15ac35fd1703c22aab34e39fdd
git.kernel.org/stable/c/8c34096c7fdf272fd4c0c37fe411cd2e3ed0ee9f
git.kernel.org/stable/c/bd502ba81cd1d515deddad7dbc6b812b14b97147
git.kernel.org/stable/c/e19478763154674c084defc62ae0d64d79657f91
launchpad.net/bugs/cve/CVE-2024-36934
nvd.nist.gov/vuln/detail/CVE-2024-36934
security-tracker.debian.org/tracker/CVE-2024-36934
www.cve.org/CVERecord?id=CVE-2024-36934