Skip to main content

Linux CVE-2026-98485

| EUVDEUVD-2026-103725
2026-10-18 Linux GHSA-mhfj-849g-frgh
View
Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

In the Linux kernel, the following vulnerability has been resolved:

netfilter: ip6t_rt: fix zero-address non-strict match out-of-bounds read

rt_mt6_check() permits rules to be configured with rtinfo->addrnr == 0 even when address matching (IP6T_RT_FST_MASK) is requested.

In the IP6T_RT_FST_NSTRICT path, rt_mt6() evaluates packet routing addresses against rtinfo->addrs[i] and terminates backwards at the bottom of the loop:

if (ipv6_addr_equal(ap, &rtinfo->addrs[i])) { i++; } if (i == rtinfo->addrnr) break;

When addrnr is 0, if the first packet address matches rtinfo->addrs[0], i is incremented to 1. Because i is now strictly greater than addrnr (0), the loop termination condition (i == rtinfo->addrnr) is bypassed and will never be satisfied.

If a crafted IPv6 packet contains matching routing addresses, i will advance past IP6T_RT_HOPS (16). The subsequent call to ipv6_addr_equal() reads beyond struct ip6t_rt, triggering UBSAN/KASAN out-of-bounds warnings or kernel panics.

Fix this by:

  1. Rejecting rules in rt_mt6_check() where IP6T_RT_FST_MASK is set but

rtinfo->addrnr is zero.

  1. In rt_mt6(), moving the termination condition (i < rtinfo->addrnr)

into the for-loop header condition and removing the backwards break at the end of the loop body.

Affected VersionsENISA

Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b89249819a7d6698bed152feafd3bc6c08489d15
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <82313c169eddc02b1bf5ba6b427803e272d3ec42
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fe336bab13834394320997de8b16ca4a913b4f13
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dd55c0ea87bf70e4e4b3b683acd29ef981335b26
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5a54f8b7f7fe207a5c14713015a5820588faf1ad
Linux patch: 6.6.158
Linux patch: 6.12.112
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <191239b0939692e92459d8d32cad14247fa93f89
Linux patch: 5.10.271
Linux patch: 6.1.189
Linux patch: 7.2.9
Linux patch: 6.18.55
Linux 2.6.12
Linux patch: 0
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <959d1829d1ce8b91b435b24a923b51bcc8897090
Linux patch: 7.3-rc5
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d9cf4ac6f326330e1fe4d95671d36a6ff3593f64
Linux patch: 5.15.222

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Oct 18, 2026 - 16:02 EUVD
CVE Published
Oct 18, 2026 - 15:16 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

Data Quality
1 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.
Awaiting Data No severity or threat signals available yet. Label will update when CVSS score is published or threat intelligence arrives.

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy