LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31685: netfilter: ip6t_eui64: reject invalid MAC header for all packets

In the Linux kernel, the following vulnerability has been resolved: netfilter: ip6t_eui64: reject invalid MAC header for all packets `eui64_mt6()` derives a modified EUI-64 from the Ethernet source address and compares it with the low 64 bits of the IPv6 source address. The existing guard only rejects an invalid MAC header when `par->fragoff != 0`. For packets with `par->fragoff == 0`, `eui64_mt6()` can still reach `eth_hdr(skb)` even when the MAC header is not valid. Fix this by removing the `par->fragoff != 0` condition so that packets with an invalid MAC header are rejected before accessing `eth_hdr(skb)`.

CriticalCVSS 9.4Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux kernel IPv6 firewall matcher can access packet data as though a valid Ethernet header exists when it does not. The supplied CVSS score is 9.4, indicating potentially severe confidentiality, integrity, and availability consequences. Actual exposure depends on whether the affected ip6t_eui64 functionality is present and used.

Executive priority

Treat as urgent where affected IPv6 firewall functionality handles untrusted traffic. Patch through supported distribution channels after targeted testing. Do not infer fleet-wide exposure solely from the critical score; rapidly inventory matcher usage and kernel fix status to focus remediation.

Technical view

The eui64_mt6() matcher derives an EUI-64 identifier from an Ethernet source address. Its prior guard rejected an invalid MAC header only for nonzero fragment offsets, allowing other packets to reach eth_hdr(skb) without a valid MAC header. The fix rejects every packet lacking a valid MAC header before that access.

Likely exposure

Prioritize Linux systems using IPv6 netfilter rules involving ip6t_eui64, particularly where untrusted IPv6 traffic reaches them. The supplied affected-version data is ambiguous and lacks CPEs, so determine exposure from vendor advisories, kernel build provenance, module availability, active rules, and inclusion of the referenced stable fix.

Exploitation context

The bundle reports no CISA KEV listing and provides no cited evidence of active exploitation or a public exploit. Network attackability and low complexity are asserted by the supplied CVSS vector, but the sources do not establish a demonstrated attack path or required deployment conditions.

Researcher notes

The record supplies no CWE, CPE, crash trace, proof of concept, or exploitation evidence. Its version data contains repeated commit identifiers and does not clearly express branch boundaries. The correction is a guard-condition change backported across multiple stable branches. Validate branch ancestry and downstream package status before declaring a host vulnerable or fixed.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable referenced stable fix.
  • Confirm the selected kernel package maps to the correct maintained branch.
  • Prioritize internet-facing or untrusted-network systems using the ip6t_eui64 matcher.
  • If updating is delayed, review whether affected matcher rules can be safely disabled.
  • Monitor Linux distribution guidance for branch-specific package and reboot requirements.

Validation and detection

  • Record running kernel versions and distribution package revisions.
  • Check whether the ip6t_eui64 functionality is available and actively referenced by firewall rules.
  • Verify vendor advisories or package changelogs include the applicable stable commit.
  • After updating, confirm systems booted into the corrected kernel.
  • Reassess IPv6 traffic paths reaching hosts that use the matcher.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-31685 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.4CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H3.95.5Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.4Critical
CVSS 3.1 vector shape for CVE-2026-31685Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.