medium
5.5
Advisory Published
Updated

CVE-2024-50038: netfilter: xtables: avoid NFPROTO_UNSPEC where needed

First published: Mon Oct 21 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: netfilter: xtables: avoid NFPROTO_UNSPEC where needed syzbot managed to call xt_cluster match via ebtables: WARNING: CPU: 0 PID: 11 at net/netfilter/xt_cluster.c:72 xt_cluster_mt+0x196/0x780 [..] ebt_do_table+0x174b/0x2a40 Module registers to NFPROTO_UNSPEC, but it assumes ipv4/ipv6 packet processing. As this is only useful to restrict locally terminating TCP/UDP traffic, register this for ipv4 and ipv6 family only. Pablo points out that this is a general issue, direct users of the set/getsockopt interface can call into targets/matches that were only intended for use with ip(6)tables. Check all UNSPEC matches and targets for similar issues: - matches and targets are fine except if they assume skb_network_header() is valid -- this is only true when called from inet layer: ip(6) stack pulls the ip/ipv6 header into linear data area. - targets that return XT_CONTINUE or other xtables verdicts must be restricted too, they are incompatbile with the ebtables traverser, e.g. EBT_CONTINUE is a completely different value than XT_CONTINUE. Most matches/targets are changed to register for NFPROTO_IPV4/IPV6, as they are provided for use by ip(6)tables. The MARK target is also used by arptables, so register for NFPROTO_ARP too. While at it, bail out if connbytes fails to enable the corresponding conntrack family. This change passes the selftests in iptables.git.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=2.6.30<5.15.168
Linux Kernel>=5.16<6.1.113
Linux Kernel>=6.2<6.6.57
Linux Kernel>=6.7<6.11.4
Linux Kernel=6.12-rc1
Linux Kernel=6.12-rc2
debian/linux<=5.10.223-1<=5.10.226-1
6.1.123-1
6.1.128-1
6.12.12-1
6.12.15-1
debian/linux-6.1
6.1.119-1~deb11u1

Remedy

https://git.kernel.org/stable/c/0bfcb7b71e735560077a42847f69597ec7dcc326

Remedy

https://git.kernel.org/stable/c/4cdc55ec6222bb195995cc58f7cb46e4d8907056

Remedy

https://git.kernel.org/stable/c/85ff9a0f793ca52c527e75cd40a69c948627ebde

Remedy

https://git.kernel.org/stable/c/8f482bb7e27b37f1f734bb9a8eeb28b23d59d189

Remedy

https://git.kernel.org/stable/c/997f67d813ce0cf5eb3cdb8f124da68141e91b6c

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-50038?

    CVE-2024-50038 has a high severity due to the potential for exploitation within the Linux kernel's networking component.

  • What systems are affected by CVE-2024-50038?

    CVE-2024-50038 affects multiple versions of the Linux kernel ranging from 2.6.30 to 6.12-rc2.

  • How do I fix CVE-2024-50038?

    To fix CVE-2024-50038, update your Linux kernel to a version that is not affected, such as those mentioned in the advisories.

  • Can CVE-2024-50038 be exploited remotely?

    Yes, CVE-2024-50038 may allow remote attackers to exploit vulnerabilities in the networking stack of the kernel.

  • Is there a workaround for CVE-2024-50038?

    Currently, there are no known workarounds for CVE-2024-50038 other than applying the appropriate kernel updates.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203