| 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-2022-49497: net: remove two BUG() from skb_checksum_help() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net: remove two BUG() from skb_checksum_help() |
| |
| I have a syzbot report that managed to get a crash in skb_checksum_help() |
| |
| If syzbot can trigger these BUG(), it makes sense to replace |
| them with more friendly WARN_ON_ONCE() since skb_checksum_help() |
| can instead return an error code. |
| |
| Note that syzbot will still crash there, until real bug is fixed. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49497 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.10.121 with commit 312c43e98ed190bd8fd7a71a0addf9539d5b8ab1 |
| Fixed in 5.15.46 with commit 6320ae1b5876c30bf98203b6a5abe8b5c45e6a04 |
| Fixed in 5.17.14 with commit d5281245f3502e960cb6b89348767b935379cee3 |
| Fixed in 5.18.3 with commit b1320c9a4d30ff54b824a8ad6036e0b5fb4c5e73 |
| Fixed in 5.19 with commit d7ea0d9df2a6265b2b180d17ebc64b38105968fc |
| |
| 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-2022-49497 |
| 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: |
| net/core/dev.c |
| |
| |
| 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/312c43e98ed190bd8fd7a71a0addf9539d5b8ab1 |
| https://git.kernel.org/stable/c/6320ae1b5876c30bf98203b6a5abe8b5c45e6a04 |
| https://git.kernel.org/stable/c/d5281245f3502e960cb6b89348767b935379cee3 |
| https://git.kernel.org/stable/c/b1320c9a4d30ff54b824a8ad6036e0b5fb4c5e73 |
| https://git.kernel.org/stable/c/d7ea0d9df2a6265b2b180d17ebc64b38105968fc |
