| 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: <2025100714-CVE-2023-53635-de6f@gregkh> Date: Tue, 7 Oct 2025 17:19:40 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53635: netfilter: conntrack: fix wrong ct->timeout value From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: fix wrong ct->timeout value (struct nf_conn)->timeout is an interval before the conntrack confirmed. After confirmed, it becomes a timestamp. It is observed that timeout of an unconfirmed conntrack: - Set by calling ctnetlink_change_timeout(). As a result, `nfct_time_stamp` was wrongly added to `ct->timeout` twice. - Get by calling ctnetlink_dump_timeout(). As a result, `nfct_time_stamp` was wrongly subtracted. Call Trace: <TASK> dump_stack_lvl ctnetlink_dump_timeout __ctnetlink_glue_build ctnetlink_glue_build __nfqnl_enqueue_packet nf_queue nf_hook_slow ip_mc_output ? __pfx_ip_finish_output ip_send_skb ? __pfx_dst_output udp_send_skb udp_sendmsg ? __pfx_ip_generic_getfrag sock_sendmsg Separate the 2 cases in: - Setting `ct->timeout` in __nf_ct_set_timeout(). - Getting `ct->timeout` in ctnetlink_dump_timeout(). Pablo appends: Update ctnetlink to set up the timeout _after_ the IPS_CONFIRMED flag is set on, otherwise conntrack creation via ctnetlink breaks. Note that the problem described in this patch occurs since the introduction of the nfnetlink_queue conntrack support, select a sufficiently old Fixes: tag for -stable kernel to pick up this fix. The Linux kernel CVE team has assigned CVE-2023-53635 to this issue. Affected and fixed versions =========================== Issue introduced in 4.4 with commit a4b4766c3cebb4018167e06b863d8e95b7274757 and fixed in 6.1.28 with commit 80c5ba0078e20d926d11d0778f9a43902664ebf0 Issue introduced in 4.4 with commit a4b4766c3cebb4018167e06b863d8e95b7274757 and fixed in 6.2.15 with commit ff5e4ac8dd7be7f1faba955c5779a68571eeb0f8 Issue introduced in 4.4 with commit a4b4766c3cebb4018167e06b863d8e95b7274757 and fixed in 6.3.2 with commit f612ae1ab4793701caf39386fb3b7f4b3ef44e48 Issue introduced in 4.4 with commit a4b4766c3cebb4018167e06b863d8e95b7274757 and fixed in 6.4 with commit 73db1b8f2bb6725b7391e85aab41fdf592b3c0c1 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-2023-53635 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 net/netfilter/nf_conntrack_netlink.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/80c5ba0078e20d926d11d0778f9a43902664ebf0 https://git.kernel.org/stable/c/ff5e4ac8dd7be7f1faba955c5779a68571eeb0f8 https://git.kernel.org/stable/c/f612ae1ab4793701caf39386fb3b7f4b3ef44e48 https://git.kernel.org/stable/c/73db1b8f2bb6725b7391e85aab41fdf592b3c0c1
Powered by blists - more mailing lists