Zurück zur Übersicht

Phoenix Contact: Use-after-free vulnerability in Linux kernel IPv4 TCP option handling in FL MGUARD 2xxx and 4xxx firmware

VDE-2026-159
Last update
18.11.2026 11:00
Published at
18.11.2026 11:00
Vendor(s)
Phoenix Contact GmbH & Co. KG
External ID
VDE-2026-159
CSAF Document

Summary

The Linux kernel used in the affected mGuard products is vulnerable to a use-after-free in the IPv4 TCP connection request option handling, which can be triggered by concurrent network traffic.

Impact

A unauthenticated remote attacker can exploit a race condition in the Linux kernel IPv4 TCP stack by sending crafted network packets, potentially leading to memory corruption, system instability, or arbitrary code execution on the mGuard device.

Affected Product(s)

Model no. Product name Affected versions
Linux Kernel 4.4, vers:generic/>=4.4|<6.1.190
1357828 FL MGUARD 2102 Firmware 10.0.0<10.7.1
1357850 FL MGUARD 2105 Firmware 10.0.0<10.7.1
1441187 FL MGUARD 4102 PCI Firmware 10.0.0<10.7.1
1488314 FL MGUARD 4102 PCI/K2 Firmware 10.0.0<10.7.1
1357842 FL MGUARD 4102 PCIE Firmware 10.0.0<10.7.1
1427378 FL MGUARD 4102 PCIE/K2 Firmware 10.0.0<10.7.1
1357840 FL MGUARD 4302 Firmware 10.0.0<10.7.1
1488318 FL MGUARD 4302/K1 Firmware 10.0.0<10.7.1
1427379 FL MGUARD 4302/K2 Firmware 10.0.0<10.7.1
1488325 FL MGUARD 4302/K3 Firmware 10.0.0<10.7.1
1488326 FL MGUARD 4302/K4 Firmware 10.0.0<10.7.1
1696708 FL MGUARD 4302/KX Firmware 10.0.0<10.7.1
1357875 FL MGUARD 4305 Firmware 10.0.0<10.7.1
1696779 FL MGUARD 4305/KX Firmware 10.0.0<10.7.1

Vulnerabilities

Expand / Collapse all

Published
16.11.2026 11:20
Weakness
Use After Free (CWE-416)
Summary

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.

References

Mitigation

Restrict external access to the device management interfaces using firewall rules. mGuard devices support filtering by incoming network interface (e.g. trusted interfaces only) or by IP address filters.

Remediation

Phoenix Contact strongly recommends upgrading affected mGuard devices to firmware version 10.7.1 or higher which fixes this vulnerability.

Acknowledgments

Phoenix Contact GmbH & Co. KG thanks the following parties for their efforts:

Revision History

Version Date Summary
1.0.0 18.11.2026 11:00 Initial revision.