Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50038, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0269ea4937343536ec7e85649932bc8c9686ea78 – < 85ff9a0f793ca52c527e75cd40a69c948627ebde
    • affected 0269ea4937343536ec7e85649932bc8c9686ea78 – < 8f482bb7e27b37f1f734bb9a8eeb28b23d59d189
    • affected 0269ea4937343536ec7e85649932bc8c9686ea78 – < 997f67d813ce0cf5eb3cdb8f124da68141e91b6c
    • affected 0269ea4937343536ec7e85649932bc8c9686ea78 – < 4cdc55ec6222bb195995cc58f7cb46e4d8907056
    • affected 0269ea4937343536ec7e85649932bc8c9686ea78 – < 0bfcb7b71e735560077a42847f69597ec7dcc326
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.57 – ≤ 6.6.*
    • unaffected 6.11.4 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50038 badge
[![CVE-2024-50038](https://cveledger.app/badge/CVE-2024-50038.svg)](https://cveledger.app/cve/CVE-2024-50038)

Record last updated .