Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 6 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-98485, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Received3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 959d1829d1ce8b91b435b24a923b51bcc8897090
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < fe336bab13834394320997de8b16ca4a913b4f13
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5a54f8b7f7fe207a5c14713015a5820588faf1ad
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b89249819a7d6698bed152feafd3bc6c08489d15
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < dd55c0ea87bf70e4e4b3b683acd29ef981335b26
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 191239b0939692e92459d8d32cad14247fa93f89
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d9cf4ac6f326330e1fe4d95671d36a6ff3593f64
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 82313c169eddc02b1bf5ba6b427803e272d3ec42
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98485 badge
[![CVE-2026-98485](https://cveledger.app/badge/CVE-2026-98485.svg)](https://cveledger.app/cve/CVE-2026-98485)

Record last updated .