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-98569

ip_gre: Reject enabling collect metadata through changelink

Description

In the Linux kernel, the following vulnerability has been resolved: ip_gre: Reject enabling collect metadata through changelink ipgre_netlink_parms() can enable collect_md on an existing GRE, GRETAP or ERSPAN device. Unlike newlink, changelink does not enforce metadata tunnel uniqueness. Converting a non-metadata device can therefore replace the metadata receive entry for another device of the same type in the same netns. Deleting either device then clears the shared entry, breaking metadata receive lookup for the surviving device. If parameter validation fails after collect_md is set, deleting the modified device can also clear an entry it never owned. Reject enabling metadata mode in both changelink callbacks before any encapsulation or tunnel parameters are modified. Allow requests that repeat the metadata attribute on an existing metadata device.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (11 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < c80315da84998b69b8829785a174b0bf72a81992
    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < cff8b520312e750ad38967c30128e1534cbf9484
    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < 1dc759571f3df14891175fc52527f7624ba01322
    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < da2e0cfbb620b199927a1e5b93b7cfde32083c7d
    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < 2e54d53b65e296b4b4bdc2cdd3b2b58dfa8d8c5c
    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < bdd41b96e814300c66222cf4e47ecb8aef995656
    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < 63c5e48d6f7f5722a48f63e13e961dc5302894ed
    • affected 2e15ea390e6f4466655066d97e22ec66870a042c – < a3f315be9d30eeb6938d11fa17fd4b32d52f7c42
  • Linux · Linux

    • affected 4.3
    • unaffected < 4.3
    • 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-98569 badge
[![CVE-2026-98569](https://cveledger.app/badge/CVE-2026-98569.svg)](https://cveledger.app/cve/CVE-2026-98569)

Record last updated .