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-74598ipv6: fix Route Information option length validation

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: fix Route Information option length validation rt6_route_rcv() validates the Route Information option (RFC 4191) length against the prefix length, but both checks are off by one. rinfo->length is the ND option length in units of 8 octets and it *includes* the 8-byte option header, so an option carrying N bytes of prefix has length == 1 + N/8. RFC 4191 section 2.3 requires length 3 when Prefix Length is greater than 64, and 2 or 3 when it is greater than 0. The code accepts length >= 2 and length >= 1 respectively. ipv6_addr_prefix() then copies prefix_len/8 bytes out of rinfo->prefix, so a Router Advertisement with (prefix_len=128, length=2) or (prefix_len=64, length=1) makes the kernel read up to 8 bytes past the end of the option. Those bytes end up in the prefix of the route that gets installed, so they are visible to userspace: # RA with a Route Information option (prefix_len=128, length=2) # followed by a source link-layer address option, 01 01 de ad be ef ca fe $ ip -6 route show 2001:db8:dead:beef:101:dead:beef:cafe via fe80::1234 dev veth0 proto ra ^^^^^^^^^^^^^^^^^^ the next option, read out of bounds When the Route Information option is the last one in the packet, those eight bytes come from the skb tail room instead. Reject the option lengths RFC 4191 does not allow.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 55 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-74598, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.43% · top 63% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < 2f6f94eda12430fb41b24b44a71e2ea4e93561d7
    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < 7eac87396c44a312be457ef41d4c5687883be9a2
    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < 7309529f257ae18e72112ef9f614edfd6df229bb
    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < 0b9e02f3bd31c888f2ccdc0ca08e546d6abe9c4d
    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < ff3cb05289b8a4ef95fa7ea14c7d34818359edbb
    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < 3b2231e358d26e3aec5d8040b1fb777af03c5f05
    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < da64ed1f346ba84df574d6469fa2e422b2511719
    • affected 70ceb4f53929f73746be72f73707cd9f8753e2fc – < d1ad8fb2ac6a1afb71dc22d9ae8efb4dda96c824
  • Linux · Linux

    • affected 2.6.17
    • unaffected < 2.6.17
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.152 – ≤ 6.6.*
    • unaffected 6.12.104 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .