[CVE-2026-53131][MODERATE 7.0] netfilter: require Ethernet MAC header before using eth_hdr() [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-53131
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: netfilter: require Ethernet MAC header before using eth_hdr() [ Upstream
Commit: 4435888e1bf139d2bfe5911643d4217382136743
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4435888e1bf139d2bfe5911643d4217382136743
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53131
Analysis date: Thu, 25 Jun 2026 05:13:43 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53131 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53131

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-53131	MODERATE	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N';*CWE-20;CWE-125;CWE-693;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N';BEST CVSS score: '4.8';DESCR 'netfilter and ipset paths could call eth_hdr(skb) without first proving that the skb belongs to an Ethernet device and that a full Ethernet MAC header is present. This can make MAC based matches or logging interpret non Ethernet packet bytes as MAC addresses, which may produce incorrect firewall decisions or misleading logs in configurations that rely on ip6t_eui64, xt_mac, ipset ip mac types, or nf_log_syslog MAC decoding. For the CVSS the PR:N is used because the attacker only needs to send packets that reach the affected filtering path and does not need a local account on the target. The base score treats this as adjacent or topology dependent because MAC based filtering is usually meaningful on local segments or controlled tunnel paths. The paranoid score uses AV:N because some deployments can expose these paths to remote traffic through routed tunnels or non Ethernet interfaces. Impact is limited confidentiality or integrity impact through possible policy bypass or exposure of packet derived MAC fields, not proven kernel memory corruption or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	REMOTE NETFILTER NETWORK SKB LOG HARDWARE LINUS IPV6 KPANIC 	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

1. ActionableScore
ActionableScore=5
ActionableScoreLower=4
Conservative score: 4
Paranoid score: 5
Final recommended bucket: **Actionable Moderate at minimum**

2. Signal breakdown

Triggered signals:
- Remote reachable / network-triggerable: +2. The affected code is in netfilter, iptables, ipset, and packet logging paths that can process packets sent by a remote peer when matching or logging rules are configured.
- Common networking core path or packet-processing path: +1. This is not a rare driver path. It is in packet filtering and logging infrastructure.
- Integrity impact plausible: +1. Incorrect interpretation of non Ethernet bytes as Ethernet MAC addresses can affect MAC based firewall or ipset matching decisions.
- Confidentiality impact plausible: +1. nf_log_syslog may log packet-derived bytes as MAC addresses, but this is limited and not a strong kernel memory disclosure primitive.

Limiting factors:
- No strong memory corruption primitive. The patch does not show UAF, OOB write, type confusion, refcount abuse, or attacker-controlled overwrite.
- No reliable kernel crash shown.
- Exploitability depends on specific rules using ip6t_eui64, xt_mac, ipset mac types, or MAC decoding logs.
- Conservative interpretation treats this as topology/configuration dependent, giving ActionableScoreLower=4.

3. Reachability analysis

A remote packet sender may trigger the affected path if the target has relevant netfilter/ipset/logging rules enabled and packet flow reaches these hooks. No local account is required for packet delivery, so PR is effectively none for the network-triggered scenario. However, rule creation itself requires administrator control, so practical exposure depends on existing firewall configuration. Containers or namespaces mainly matter if they can install or influence netfilter rules, but the more important case is a host already using MAC based matching or MAC logging on traffic that may arrive through non Ethernet or tunnel paths.

4. Severity interpretation

This behaves more like Actionable Moderate than Important. The issue is security-relevant because it is in network packet filtering and can plausibly cause policy bypass or misleading security logs. Theoretical memory safety concern is limited to invalid Ethernet header interpretation or bounded reads from skb data. The patch does not support privilege escalation, arbitrary write, strong memory corruption, or reliable DoS. Manual review is still justified because firewall policy correctness is affected and some deployments may expose the path to remote traffic.

5. One-sentence report phrase

netfilter and ipset could use eth_hdr(skb) without confirming an Ethernet device and a full MAC header, allowing remote traffic in affected configurations to influence MAC based matching or logging through invalid Ethernet header interpretation.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED.
Reason: network packet filtering paths and possible firewall policy impact make this actionable, but absence of a concrete memory corruption or crash primitive keeps it below Important by default.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: netfilter: require Ethernet MAC header before using eth_hdr() [ Upstream
Commit: 4435888e1bf139d2bfe5911643d4217382136743
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4435888e1bf139d2bfe5911643d4217382136743

Changed files:
  net/ipv6/netfilter/ip6t_eui64.c
  net/netfilter/ipset/ip_set_bitmap_ipmac.c
  net/netfilter/ipset/ip_set_hash_ipmac.c
  net/ip.h
  net/ipv6.h
  net/netfilter/ipset/ip_set_hash_mac.c
  net/netlink.h
  net/netfilter/nf_log_syslog.c
  net/netfilter/xt_mac.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4435888e1bf139d2bfe5911643d4217382136743

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53131 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53131

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
  The Best / paranoid CVSS vector: AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
  The Best / paranoid CVSS score: 4.8

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 4
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).