| 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: <2025022617-CVE-2022-49561-3e6a@gregkh> Date: Wed, 26 Feb 2025 03:13:55 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49561: netfilter: conntrack: re-fetch conntrack after insertion Description =========== In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: re-fetch conntrack after insertion In case the conntrack is clashing, insertion can free skb->_nfct and set skb->_nfct to the already-confirmed entry. This wasn't found before because the conntrack entry and the extension space used to free'd after an rcu grace period, plus the race needs events enabled to trigger. The Linux kernel CVE team has assigned CVE-2022-49561 to this issue. Affected and fixed versions =========================== Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 4.14.282 with commit e97222b785e70e8973281666d709baad6523d8af Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 4.19.246 with commit 92a999d1963eed0df666284e20055136ceabd12f Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 5.4.197 with commit b16bb373988da3ceb0308381634117e18b6ec60d Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 5.10.120 with commit 91a36ec160ec1a0c8f5352b772dffcbb0b6023e3 Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 5.15.45 with commit 01989d7eebb61c99bd4b88ebc8e261bd2f02caed Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 5.17.13 with commit 04f9e9104c969d8ce10a4a43634f641ed082092d Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 5.18.2 with commit 04e4a11dc723c52db7a36dc58f0d69ce6426f8f0 Issue introduced in 4.7 with commit 71d8c47fc653711c41bc3282e5b0e605b3727956 and fixed in 5.19 with commit 56b14ecec97f39118bf85c9ac2438c5a949509ed 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-49561 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: include/net/netfilter/nf_conntrack_core.h 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/e97222b785e70e8973281666d709baad6523d8af https://git.kernel.org/stable/c/92a999d1963eed0df666284e20055136ceabd12f https://git.kernel.org/stable/c/b16bb373988da3ceb0308381634117e18b6ec60d https://git.kernel.org/stable/c/91a36ec160ec1a0c8f5352b772dffcbb0b6023e3 https://git.kernel.org/stable/c/01989d7eebb61c99bd4b88ebc8e261bd2f02caed https://git.kernel.org/stable/c/04f9e9104c969d8ce10a4a43634f641ed082092d https://git.kernel.org/stable/c/04e4a11dc723c52db7a36dc58f0d69ce6426f8f0 https://git.kernel.org/stable/c/56b14ecec97f39118bf85c9ac2438c5a949509ed
Powered by blists - more mailing lists