CVE-2026-98485: netfilter: ip6t_rt: fix zero-address non-strict match out-of-bounds read
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 191239b0939692e92459d8d32cad14247fa93f89, 5a54f8b7f7fe207a5c14713015a5820588faf1ad, 82313c169eddc02b1bf5ba6b427803e272d3ec42; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 191239b0939692e92459d8d32cad14247fa93f89, 5a54f8b7f7fe207a5c14713015a5820588faf1ad, 82313c169eddc02b1bf5ba6b427803e272d3ec42; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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. 2. 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.
- Published
- Oct 18, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 959d1829d1ce8b91b435b24a923b51bcc8897090affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fe336bab13834394320997de8b16ca4a913b4f13affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5a54f8b7f7fe207a5c14713015a5820588faf1adaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b89249819a7d6698bed152feafd3bc6c08489d15affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before dd55c0ea87bf70e4e4b3b683acd29ef981335b26affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 191239b0939692e92459d8d32cad14247fa93f89affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d9cf4ac6f326330e1fe4d95671d36a6ff3593f64affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 82313c169eddc02b1bf5ba6b427803e272d3ec42affected · git
- before 2.6.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98483Oct 18, 2026 · nfc: fix use-after-free in nfc_get_local_general_bytes0Monitor
- ← EarlierCVE-2026-98484Oct 18, 2026 · netfilter: nf_tables: skip expired catchall elements on insert and delete0Monitor
- Later →CVE-2026-98486Oct 18, 2026 · net: ena: fix MMIO read buffer leak on probe failure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 191239b0939692e92459d8d32cad14247fa93f89 | Vendor (CNA) |
| Linux Linux | 5a54f8b7f7fe207a5c14713015a5820588faf1ad | Vendor (CNA) |
| Linux Linux | 82313c169eddc02b1bf5ba6b427803e272d3ec42 | Vendor (CNA) |
| Linux Linux | 959d1829d1ce8b91b435b24a923b51bcc8897090 | Vendor (CNA) |
| Linux Linux | b89249819a7d6698bed152feafd3bc6c08489d15 | Vendor (CNA) |
| Linux Linux | d9cf4ac6f326330e1fe4d95671d36a6ff3593f64 | Vendor (CNA) |
| Linux Linux | dd55c0ea87bf70e4e4b3b683acd29ef981335b26 | Vendor (CNA) |
| Linux Linux | fe336bab13834394320997de8b16ca4a913b4f13 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 2, 2026+15 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 7.1
- Severity— → high
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5a54f8b7f7fe207a5c14713015a5820588faf1ad
- git.kernel.org/stable/c/82313c169eddc02b1bf5ba6b427803e272d3ec42
- git.kernel.org/stable/c/959d1829d1ce8b91b435b24a923b51bcc8897090
- git.kernel.org/stable/c/b89249819a7d6698bed152feafd3bc6c08489d15
- git.kernel.org/stable/c/d9cf4ac6f326330e1fe4d95671d36a6ff3593f64
- git.kernel.org/stable/c/dd55c0ea87bf70e4e4b3b683acd29ef981335b26
- git.kernel.org/stable/c/fe336bab13834394320997de8b16ca4a913b4f13
Vendor advisories and official records. Exploit/PoC links are deliberately left out.