| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025061844-CVE-2022-50213-bc19@gregkh> Date: Wed, 18 Jun 2025 13:04:38 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2022-50213: netfilter: nf_tables: do not allow SET_ID to refer to another table From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: do not allow SET_ID to refer to another table When doing lookups for sets on the same batch by using its ID, a set from a different table can be used. Then, when the table is removed, a reference to the set may be kept after the set is freed, leading to a potential use-after-free. When looking for sets by ID, use the table that was used for the lookup by name, and only return sets belonging to that same table. This fixes CVE-2022-2586, also reported as ZDI-CAN-17470. The Linux kernel CVE team has assigned CVE-2022-50213 to this issue. Affected and fixed versions =========================== Issue introduced in 3.16 with commit 958bee14d0718ca7a5002c0f48a099d1d345812a and fixed in 4.19.256 with commit 77d3b5038b7462318f5183e2ad704b01d57215a2 Issue introduced in 3.16 with commit 958bee14d0718ca7a5002c0f48a099d1d345812a and fixed in 5.4.211 with commit fab2f61cc3b0e441b1749f017cfee75f9bbaded7 Issue introduced in 3.16 with commit 958bee14d0718ca7a5002c0f48a099d1d345812a and fixed in 5.10.137 with commit 1a4b18b1ff11ba26f9a852019d674fde9d1d1cff Issue introduced in 3.16 with commit 958bee14d0718ca7a5002c0f48a099d1d345812a and fixed in 5.15.61 with commit faafd9286f1355c76fe9ac3021c280297213330e Issue introduced in 3.16 with commit 958bee14d0718ca7a5002c0f48a099d1d345812a and fixed in 5.18.18 with commit f4fa03410f7c5f5bd8f90e9c11e9a8c4b526ff6f Issue introduced in 3.16 with commit 958bee14d0718ca7a5002c0f48a099d1d345812a and fixed in 5.19.2 with commit 0d07039397527361850c554c192e749cfc879ea9 Issue introduced in 3.16 with commit 958bee14d0718ca7a5002c0f48a099d1d345812a and fixed in 6.0 with commit 470ee20e069a6d05ae549f7d0ef2bdbcee6a81b2 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-50213 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/netfilter/nf_tables_api.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/77d3b5038b7462318f5183e2ad704b01d57215a2 https://git.kernel.org/stable/c/fab2f61cc3b0e441b1749f017cfee75f9bbaded7 https://git.kernel.org/stable/c/1a4b18b1ff11ba26f9a852019d674fde9d1d1cff https://git.kernel.org/stable/c/faafd9286f1355c76fe9ac3021c280297213330e https://git.kernel.org/stable/c/f4fa03410f7c5f5bd8f90e9c11e9a8c4b526ff6f https://git.kernel.org/stable/c/0d07039397527361850c554c192e749cfc879ea9 https://git.kernel.org/stable/c/470ee20e069a6d05ae549f7d0ef2bdbcee6a81b2
Powered by blists - more mailing lists