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-74474vxlan: use pskb_network_may_pull() for transmit path header pulls

Description

In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskb_network_may_pull() for transmit path header pulls In vxlan_xmit(), arp_reduce(), and vxlan_mdb_entry_skb_get(), pskb_may_pull() was being called to verify the availability of network layer headers (ARP, IPv6/ND, IP/IPv6 MDB keys). However, during transmit skb->data points to the MAC header, so skb_network_offset(skb) is ETH_HLEN (14 bytes). Using pskb_may_pull(skb, len) only checks len bytes from skb->data rather than skb_network_offset(skb) + len, which can leave part of the network header in non-linear frags. Replace these remaining pskb_may_pull() calls with pskb_network_may_pull() to properly account for the MAC header offset.

Timeline

  1. ID reserved

    By Linux

  2. 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-74474, 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.49% · top 57% of all CVEs (16 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 e4f67addf158f98f8197e08974966b18480dc751 – < 371425d4be7795e9158388af9eee0201e6047410
    • affected e4f67addf158f98f8197e08974966b18480dc751 – < bb01c51950c3ff3c76acdd54b85ab38ccc2a8bb4
    • affected e4f67addf158f98f8197e08974966b18480dc751 – < 6146901881f09ef063eb34ad389f63231f8486f5
    • affected e4f67addf158f98f8197e08974966b18480dc751 – < 94dee751aad627b3645d424b5d0c736d394573e9
    • affected e4f67addf158f98f8197e08974966b18480dc751 – < 7076a34b6e33315dc160b4612bfea1c597495585
    • affected e4f67addf158f98f8197e08974966b18480dc751 – < b9553558b48db54ac9273e6b98d7263ef5c1a329
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .