| # https://nvd.nist.gov/vuln/detail/CVE-2022-3523 |
| # Introduced in version v2.6.12 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| # Patched in kernel since v6.1 16ce101db85db694a91380aa4c89b25530871d33 |
| CVE_CHECK_IGNORE += "CVE-2022-3523" |
| |
| # https://nvd.nist.gov/vuln/detail/CVE-2022-3566 |
| # Introduced in version v2.6.12 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| # Patched in kernel since v6.1 f49cd2f4d6170d27a2c61f1fecb03d8a70c91f57 |
| CVE_CHECK_IGNORE += "CVE-2022-3566" |
| |
| # https://nvd.nist.gov/vuln/detail/CVE-2022-3567 |
| # Introduced in version v2.6.12 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| # Patched in kernel since v6.1 364f997b5cfe1db0d63a390fe7c801fa2b3115f6 |
| CVE_CHECK_IGNORE += "CVE-2022-3567" |
| |
| |
| # 2023 |
| |
| # https://nvd.nist.gov/vuln/detail/CVE-2022-38457 |
| # https://nvd.nist.gov/vuln/detail/CVE-2022-40133 |
| # Both CVE-2022-38457 & CVE-2022-40133 are fixed by the same commit: |
| # Introduced in version v4.20 e14c02e6b6990e9f6ee18a214a22ac26bae1b25e |
| # Patched in kernel since v6.2 a309c7194e8a2f8bd4539b9449917913f6c2cd50 |
| # Backported in version v6.1.7 7ac9578e45b20e3f3c0c8eb71f5417a499a7226a |
| # See: |
| # * https://www.linuxkernelcves.com/cves/CVE-2022-38457 |
| # * https://www.linuxkernelcves.com/cves/CVE-2022-40133 |
| # * https://lore.kernel.org/all/CAODzB9q3OBD0k6W2bcWrSZo2jC3EvV0PrLyWmO07rxR4nQgkJA@mail.gmail.com/T/ |
| CVE_CHECK_IGNORE += "CVE-2022-38457 CVE-2022-40133" |
| |
| # https://nvd.nist.gov/vuln/detail/CVE-2023-1075 |
| # Introduced in v4.20 a42055e8d2c30d4decfc13ce943d09c7b9dad221 |
| # Patched in kernel v6.2 ffe2a22562444720b05bdfeb999c03e810d84cbb |
| # Backported in version 6.1.11 37c0cdf7e4919e5f76381ac60817b67bcbdacb50 |
| # 5.15 still has issue, include/net/tls.h:is_tx_ready() would need patch |
| CVE_CHECK_IGNORE += "CVE-2023-1075" |