Fedora Account System
Red Hat Associate
Red Hat Customer
In the Linux kernel, the following vulnerability has been resolved: ipv4: free inet_opt and ireq_opt after an RCU grace period tcp_v4_syn_recv_sock() transfers ownership of ireq->ireq_opt to the child socket (newinet->inet_opt) without copying it. Another cpu can concurrently process a retransmitted SYN for the same request socket, and send a SYNACK from tcp_check_req(). tcp_v4_send_synack() and inet_csk_route_req() read ireq->ireq_opt under rcu_read_lock() only, and ip_build_and_send_pkt() and ip_options_build() then read opt->optlen twice. Note that the SYNACK timer itself is not an issue: it holds a reference on its request socket, and inet_csk_reqsk_queue_drop() calls timer_delete_sync() before the child can be freed. Since commit 079096f103fa ("tcp/dccp: install syn_recv requests into ehash table"), request sockets are processed without holding the listener lock, so nothing prevents the child socket from being freed while the SYNACK is still being built. TCP child sockets do not have SOCK_RCU_FREE, and inet_sock_destruct() frees inet_opt with a plain kfree(), leading to a use-after-free in ip_options_build(). A similar issue exists with request socket migration (net.ipv4.tcp_migrate_req=1, or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program). reqsk_timer_handler() clones the request socket with inet_reqsk_clone(), so that the old request socket and its clone share the same ireq_opt, then reqsk_migrate_reset() clears the pointer in the old one. Another cpu holding a reference on the old request socket can still be using these options (sending a SYNACK, or creating a child in tcp_v4_syn_recv_sock()) when the clone is freed, and tcp_v4_reqsk_destructor() also uses a plain kfree(). Readers already use RCU, and other paths replacing inet_opt (do_ip_setsockopt(), cipso_v4_sock_setattr()...) already use kfree_rcu(). Use kfree_rcu() in inet_sock_destruct() and tcp_v4_reqsk_destructor() as well. IPv6 is not affected by the first issue, because tcp_v6_syn_recv_sock() duplicates the options. tcp_v6_reqsk_destructor() has the same migration issue with ipv6_opt, which is only set by CALIPSO. This will be addressed in a separate patch.
Upstream advisory: https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98432.mbox
I would like to ask whether the following kernel settings could provide partial mitigation for CVE-2026-98432. According to the upstream CVE announcement, one of the UAF paths involves request socket migration when `net.ipv4.tcp_migrate_req=1` or a `BPF_SK_REUSEPORT_SELECT_OR_MIGRATE` program is used. Anthropic also demonstrated remote root code execution against a Linux server with an MPTCP listener. In my AlmaLinux environment, both parameters are disabled: net.ipv4.tcp_migrate_req = 0 net.mptcp.enabled = 0 I understand that the normal TCP SYN retransmission path remains vulnerable and that these settings do not fully mitigate the issue. However, could these settings reduce the attack surface and serve as a partial mitigation until a kernel fix is available? I would appreciate Red Hat Product Security's assessment for RHEL 8, 9, and 10. References: https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98432.mbox https://www.anthropic.com/research/discovering-vulnerabilities-with-claude Best regards, Akiyoshi Kurita
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:93415 https://access.redhat.com/errata/RHSA-2026:93415
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:93414 https://access.redhat.com/errata/RHSA-2026:93414
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:93412 https://access.redhat.com/errata/RHSA-2026:93412
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:93413 https://access.redhat.com/errata/RHSA-2026:93413
This issue has been addressed in the following products: NVIDIA for RHEL 10 Via RHSA-2026:93775 https://access.redhat.com/errata/RHSA-2026:93775
https://access.redhat.com/security/cve/cve-2026-98432 is missing all the supported minor releases - 9.2/4/6 etc
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions Via RHSA-2026:94109 https://access.redhat.com/errata/RHSA-2026:94109
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2026:94303 https://access.redhat.com/errata/RHSA-2026:94303
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:94438 https://access.redhat.com/errata/RHSA-2026:94438
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:94477 https://access.redhat.com/errata/RHSA-2026:94477
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:94508 https://access.redhat.com/errata/RHSA-2026:94508
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:94558 https://access.redhat.com/errata/RHSA-2026:94558
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On Via RHSA-2026:94623 https://access.redhat.com/errata/RHSA-2026:94623
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On Via RHSA-2026:94996 https://access.redhat.com/errata/RHSA-2026:94996
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.22 Via RHSA-2026:95346 https://access.redhat.com/errata/RHSA-2026:95346
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.21 Via RHSA-2026:95408 https://access.redhat.com/errata/RHSA-2026:95408
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.20 Via RHSA-2026:95377 https://access.redhat.com/errata/RHSA-2026:95377
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2026:95523 https://access.redhat.com/errata/RHSA-2026:95523
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.12 Via RHSA-2026:95416 https://access.redhat.com/errata/RHSA-2026:95416
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 5.0 Via RHSA-2026:94537 https://access.redhat.com/errata/RHSA-2026:94537
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2026:95508 https://access.redhat.com/errata/RHSA-2026:95508
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:97873 https://access.redhat.com/errata/RHSA-2026:97873
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2026:95745 https://access.redhat.com/errata/RHSA-2026:95745
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2026:96282 https://access.redhat.com/errata/RHSA-2026:96282
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:98608 https://access.redhat.com/errata/RHSA-2026:98608
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2026:95755 https://access.redhat.com/errata/RHSA-2026:95755
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2026:95104 https://access.redhat.com/errata/RHSA-2026:95104