| 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-49725: i40e: Fix call trace in setup_tx_descriptors |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| i40e: Fix call trace in setup_tx_descriptors |
| |
| After PF reset and ethtool -t there was call trace in dmesg |
| sometimes leading to panic. When there was some time, around 5 |
| seconds, between reset and test there were no errors. |
| |
| Problem was that pf reset calls i40e_vsi_close in prep_for_reset |
| and ethtool -t calls i40e_vsi_close in diag_test. If there was not |
| enough time between those commands the second i40e_vsi_close starts |
| before previous i40e_vsi_close was done which leads to crash. |
| |
| Add check to diag_test if pf is in reset and don't start offline |
| tests if it is true. |
| Add netif_info("testing failed") into unhappy path of i40e_diag_test() |
| |
| The Linux kernel CVE team has assigned CVE-2022-49725 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.2 with commit e17bc411aea8fbebc51857037f104ab09f765120 and fixed in 4.14.285 with commit 5ba9956ca57e361fb13ea369bb753eb33177acc7 |
| Issue introduced in 4.2 with commit e17bc411aea8fbebc51857037f104ab09f765120 and fixed in 4.19.249 with commit 15950157e2c24865b696db1c9ccc72743ae0e967 |
| Issue introduced in 4.2 with commit e17bc411aea8fbebc51857037f104ab09f765120 and fixed in 5.4.200 with commit ff6e03fe84bc917bb0c907d02de668c2fe101712 |
| Issue introduced in 4.2 with commit e17bc411aea8fbebc51857037f104ab09f765120 and fixed in 5.10.124 with commit 814092927a215f5ca6c08249ec72a205e0b473cd |
| Issue introduced in 4.2 with commit e17bc411aea8fbebc51857037f104ab09f765120 and fixed in 5.15.49 with commit 0a4e5a3dc5e41212870e6043895ae02455c93f63 |
| Issue introduced in 4.2 with commit e17bc411aea8fbebc51857037f104ab09f765120 and fixed in 5.18.6 with commit 322271351b0e41565171e4cce70ea41854fac115 |
| Issue introduced in 4.2 with commit e17bc411aea8fbebc51857037f104ab09f765120 and fixed in 5.19 with commit fd5855e6b1358e816710afee68a1d2bc685176ca |
| |
| 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-49725 |
| 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/intel/i40e/i40e_ethtool.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/5ba9956ca57e361fb13ea369bb753eb33177acc7 |
| https://git.kernel.org/stable/c/15950157e2c24865b696db1c9ccc72743ae0e967 |
| https://git.kernel.org/stable/c/ff6e03fe84bc917bb0c907d02de668c2fe101712 |
| https://git.kernel.org/stable/c/814092927a215f5ca6c08249ec72a205e0b473cd |
| https://git.kernel.org/stable/c/0a4e5a3dc5e41212870e6043895ae02455c93f63 |
| https://git.kernel.org/stable/c/322271351b0e41565171e4cce70ea41854fac115 |
| https://git.kernel.org/stable/c/fd5855e6b1358e816710afee68a1d2bc685176ca |
