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-72319ipvs: ensure inner headers in ICMP errors are in headroom

Description

In the Linux kernel, the following vulnerability has been resolved: ipvs: ensure inner headers in ICMP errors are in headroom Sashiko points out that after stripping the outer headers with pskb_pull() we should ensure the inner IP headers in ICMP errors from tunnels are present in the skb headroom for functions like ipv4_update_pmtu(), icmp_send() and IP_VS_DBG(). Also, add more checks for the length of the inner headers.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 months 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-72319, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.74% · top 44% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < 19657b3a17b774ae4e2f2635b5ae8638c9344a40
    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < dac813101914c21219ac221a60a31a11bc90e7ec
    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < dd22f74a09e25ca298ced0a3763ef353242cb78d
    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < 9bc9b95aee2b2e3f1301a16a67ee504960402875
    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < a735f9964a3d9ed97daf9b08507f8b5bcafe6326
    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < 8f48cfe657409fb5c7ba0521b14da6d47546d9cf
    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < 92185d6f7819bc558939ae83de7b1abe90e3b5c2
    • affected f2edb9f7706dcb2c0d9a362b2ba849efe3a97f5e – < 3f7a535ff0fa627a0132803e4c2f903ceffcbc1c
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 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-72319 badge
[![CVE-2026-72319](https://cveledger.app/badge/CVE-2026-72319.svg)](https://cveledger.app/cve/CVE-2026-72319)

Record last updated .