| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-53010: bnxt: Do not read past the end of test names |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bnxt: Do not read past the end of test names |
| |
| Test names were being concatenated based on a offset beyond the end of |
| the first name, which tripped the buffer overflow detection logic: |
| |
| detected buffer overflow in strnlen |
| [...] |
| Call Trace: |
| bnxt_ethtool_init.cold+0x18/0x18 |
| |
| Refactor struct hwrm_selftest_qlist_output to use an actual array, |
| and adjust the concatenation to use snprintf() rather than a series of |
| strncat() calls. |
| |
| The Linux kernel CVE team has assigned CVE-2023-53010 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.12 with commit eb51365846bc418687af4c4f41b68b6e84cdd449 and fixed in 6.1.9 with commit cefa85480ac99c0bef5a09daadb48d65fc28e279 |
| Issue introduced in 4.12 with commit eb51365846bc418687af4c4f41b68b6e84cdd449 and fixed in 6.2 with commit d3e599c090fc6977331150c5f0a69ab8ce87da21 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2023-53010 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/net/ethernet/broadcom/bnxt/bnxt_ethtool.c |
| drivers/net/ethernet/broadcom/bnxt/bnxt_hsi.h |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/cefa85480ac99c0bef5a09daadb48d65fc28e279 |
| https://git.kernel.org/stable/c/d3e599c090fc6977331150c5f0a69ab8ce87da21 |