CVE-2026-31424 — netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP
In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP Weiming Shi says: xt_match and xt_target structs registered with NFPROTO_UNSPEC can be loaded by any protocol family through nft_compat. When such a match/target sets .hooks to restrict which hooks it may run on, the bitmask uses NF_INET_* constants. This is only correct for families whose hook layout matches NF_INET_*: IPv4, IPv6, INET, and bridge all share the same five hooks (PRE_ROUTING ... POST_ROUTING). ARP only has three hooks (IN=0, OUT=1, FORWARD=2) with different semantics. Because NF_ARP_OUT == 1 == NF_INET_LOCAL_IN, the .hooks validation silently passes for the wrong reasons, allowing matches to run on ARP chains where the hook assumptions (e.g. state->in being set on input hooks) do not hold. This leads to NULL pointer dereferences; xt_devgroup is one concrete example: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000044: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000220-0x0000000000000227] RIP: 0010:devgroup_mt+0xff/0x350 Call Trace: <TASK> nft_match_eval (net/netfilter/nft_compat.c:407) nft_do_chain (net/netfilter/nf_tables_core.c:285) nft_do_chain_arp (net/netfilter/nft_chain_filter.c:61) nf_hook_slow (net/netfilter/core.c:623) arp_xmit (net/ipv4/arp.c:666) </TASK> Kernel panic - not syncing: Fatal exception in interrupt Fix it by restricting arptables to NFPROTO_ARP extensions only. Note that arptables-legacy only supports: - arpt_CLASSIFY - arpt_mangle - arpt_MARK that provide explicit NFPROTO_ARP match/target declarations.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 2.6.39≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < 3d5d488f11776738deab9da336038add95d342d1≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < 3e79374b03bf9a2f282f0eb1d0ac3776f7e0f28a≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < dc3e27dd7d76e21106b8f9bbdc31f5da74a89014≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < e7e1b6bcb389c8708003d40613a59ff2496f6b1f≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < f00ac65c90ea475719e08d629e2e26c8b4e6999b≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < 1cd6313c8644bfebbd813a05da9daa21b09dd68c≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < d9a0af9e43416aa50c0595e15fa01365a1c72c49 and 1 more≥ 9291747f118d6404e509747b85ff5f6dfec368d2 and < 80e3c75f71c3ea1e62fcb032382de13e00a68f8b |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 7.0-rc5version 7.0-rc6≥ 2.6.39 and < 5.10.253version 7.0-rc4version 7.0-rc3version 7.0-rc2version 7.0-rc1≥ 6.19 and < 6.19.12 and 5 more≥ 6.13 and < 6.18.22≥ 6.7 and < 6.12.81≥ 6.2 and < 6.6.134≥ 5.16 and < 6.1.168≥ 5.11 and < 5.15.203 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
13 on the record
- git.kernel.org/stable/c/3e79374b03bf9a2f282f0eb1d0ac3776f7e0f28a
- git.kernel.org/stable/c/80e3c75f71c3ea1e62fcb032382de13e00a68f8b
- git.kernel.org/stable/c/f00ac65c90ea475719e08d629e2e26c8b4e6999b
- git.kernel.org/stable/c/3d5d488f11776738deab9da336038add95d342d1
- git.kernel.org/stable/c/1cd6313c8644bfebbd813a05da9daa21b09dd68c
- git.kernel.org/stable/c/d9a0af9e43416aa50c0595e15fa01365a1c72c49
- git.kernel.org/stable/c/dc3e27dd7d76e21106b8f9bbdc31f5da74a89014
- git.kernel.org/stable/c/e7e1b6bcb389c8708003d40613a59ff2496f6b1f
- github.com/advisories/GHSA-9r6p-6xq4-mrq9
- cert-portal.siemens.com/productcert/html/ssa-082556.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- nvd.nist.gov/vuln/detail/CVE-2026-31424
- cert-portal.siemens.com/productcert/html/ssa-019113.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-31424 is "netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.