| 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-2024-53120: net/mlx5e: CT: Fix null-ptr-deref in add rule err flow |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net/mlx5e: CT: Fix null-ptr-deref in add rule err flow |
| |
| In error flow of mlx5_tc_ct_entry_add_rule(), in case ct_rule_add() |
| callback returns error, zone_rule->attr is used uninitiated. Fix it to |
| use attr which has the needed pointer value. |
| |
| Kernel log: |
| BUG: kernel NULL pointer dereference, address: 0000000000000110 |
| RIP: 0010:mlx5_tc_ct_entry_add_rule+0x2b1/0x2f0 [mlx5_core] |
| … |
| Call Trace: |
| <TASK> |
| ? __die+0x20/0x70 |
| ? page_fault_oops+0x150/0x3e0 |
| ? exc_page_fault+0x74/0x140 |
| ? asm_exc_page_fault+0x22/0x30 |
| ? mlx5_tc_ct_entry_add_rule+0x2b1/0x2f0 [mlx5_core] |
| ? mlx5_tc_ct_entry_add_rule+0x1d5/0x2f0 [mlx5_core] |
| mlx5_tc_ct_block_flow_offload+0xc6a/0xf90 [mlx5_core] |
| ? nf_flow_offload_tuple+0xd8/0x190 [nf_flow_table] |
| nf_flow_offload_tuple+0xd8/0x190 [nf_flow_table] |
| flow_offload_work_handler+0x142/0x320 [nf_flow_table] |
| ? finish_task_switch.isra.0+0x15b/0x2b0 |
| process_one_work+0x16c/0x320 |
| worker_thread+0x28c/0x3a0 |
| ? __pfx_worker_thread+0x10/0x10 |
| kthread+0xb8/0xf0 |
| ? __pfx_kthread+0x10/0x10 |
| ret_from_fork+0x2d/0x50 |
| ? __pfx_kthread+0x10/0x10 |
| ret_from_fork_asm+0x1a/0x30 |
| </TASK> |
| |
| The Linux kernel CVE team has assigned CVE-2024-53120 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.14 with commit 7fac5c2eced36f335ee19ff316bd3182fbeda823 and fixed in 5.15.174 with commit 882f392d9e3649557e71efd78ae20c86039ffb7c |
| Issue introduced in 5.14 with commit 7fac5c2eced36f335ee19ff316bd3182fbeda823 and fixed in 6.1.119 with commit 0c7c70ff8b696cfedba350411dca736361ef9a0f |
| Issue introduced in 5.14 with commit 7fac5c2eced36f335ee19ff316bd3182fbeda823 and fixed in 6.6.63 with commit 06dc488a593020bd2f006798557d2a32104d8359 |
| Issue introduced in 5.14 with commit 7fac5c2eced36f335ee19ff316bd3182fbeda823 and fixed in 6.11.10 with commit 6030f8bd7902e9e276a0edc09bf11979e4e2bc2e |
| Issue introduced in 5.14 with commit 7fac5c2eced36f335ee19ff316bd3182fbeda823 and fixed in 6.12 with commit e99c6873229fe0482e7ceb7d5600e32d623ed9d9 |
| |
| 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-2024-53120 |
| 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/mellanox/mlx5/core/en/tc_ct.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/882f392d9e3649557e71efd78ae20c86039ffb7c |
| https://git.kernel.org/stable/c/0c7c70ff8b696cfedba350411dca736361ef9a0f |
| https://git.kernel.org/stable/c/06dc488a593020bd2f006798557d2a32104d8359 |
| https://git.kernel.org/stable/c/6030f8bd7902e9e276a0edc09bf11979e4e2bc2e |
| https://git.kernel.org/stable/c/e99c6873229fe0482e7ceb7d5600e32d623ed9d9 |
