CVE-2026-31700

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd()

In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via __packet_snd_vnet_parse() but then re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent userspace thread can modify the vnet_hdr fields between validation and use, bypassing all safety checks.

The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr to a stack-local variable. All other vnet_hdr consumers in the kernel (tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX path is the only caller of virtio_net_hdr_to_skb() that reads directly from user-controlled shared memory.

Fix this by copying vnet_hdr from the mmap'd ring buffer to a stack-local variable before validation and use, consistent with the approach used in packet_snd() and all other callers.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
1.2%
KEV
Not listed

Published

May 1, 2026

Last Modified

June 19, 2026

Advisory Details (5)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74e2db36fe50e3ad9d5300d7fd0e6e2a15a6d121
generic

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48a6ef291a17639e1b6ae0fbe9c8b2bb87d7804b
generic

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a1bf9116ea31470b89692585c3910dfe830dcdd
generic

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c054e17d9d41f1020376806c7f750834ced4dc5
generic

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28324a3b62d9ce7f9bdd65a8ce63f382041d1b27

Vendor Advisories for CVE-2026-31700(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 151 total refreshes for this CVE.

  1. 2026-07-13 22:30 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
Show 75 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-17 17:53 UTCEPSS rescore
  3. 2026-06-16 17:52 UTCEPSS rescore
  4. 2026-06-15 17:49 UTCEPSS rescore
  5. 2026-06-14 23:18 UTCEPSS rescore
  6. 2026-06-14 21:36 UTCEG score recompute
  7. 2026-06-14 21:36 UTCVendor advisory
  8. 2026-06-14 21:36 UTCGHSA enrichment
  9. 2026-06-14 09:12 UTCEG score recompute
  10. 2026-06-14 09:12 UTCVendor advisory
  11. 2026-06-14 09:12 UTCGHSA enrichment
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 05:50 UTCEG score recompute
  16. 2026-06-12 05:50 UTCGHSA enrichment
  17. 2026-06-11 17:26 UTCEG score recompute
  18. 2026-06-11 17:26 UTCVendor advisory
  19. 2026-06-11 17:26 UTCGHSA enrichment
  20. 2026-06-11 14:00 UTCEPSS rescore
  21. 2026-06-11 03:39 UTCEG score recompute
  22. 2026-06-11 03:39 UTCVendor advisory
  23. 2026-06-11 03:39 UTCGHSA enrichment
  24. 2026-06-10 22:18 UTCEPSS rescore
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-10 12:46 UTCEG score recompute
  27. 2026-06-10 12:46 UTCVendor advisory
  28. 2026-06-10 12:46 UTCGHSA enrichment
  29. 2026-06-10 00:21 UTCEG score recompute
  30. 2026-06-10 00:21 UTCVendor advisory
  31. 2026-06-10 00:21 UTCGHSA enrichment
  32. 2026-06-09 11:57 UTCEG score recompute
  33. 2026-06-09 11:57 UTCVendor advisory
  34. 2026-06-09 11:56 UTCGHSA enrichment
  35. 2026-06-08 23:31 UTCEG score recompute
  36. 2026-06-08 23:31 UTCVendor advisory
  37. 2026-06-08 23:31 UTCGHSA enrichment
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 04:27 UTCEG score recompute
  41. 2026-06-08 04:27 UTCVendor advisory
  42. 2026-06-08 04:27 UTCGHSA enrichment
  43. 2026-06-07 16:03 UTCEG score recompute
  44. 2026-06-07 16:03 UTCVendor advisory
  45. 2026-06-07 16:03 UTCGHSA enrichment
  46. 2026-06-07 15:25 UTCEPSS rescore
  47. 2026-06-07 15:25 UTCEPSS rescore
  48. 2026-06-07 15:25 UTCEPSS rescore
  49. 2026-06-07 03:38 UTCEG score recompute
  50. 2026-06-07 03:38 UTCVendor advisory
  51. 2026-06-07 03:38 UTCGHSA enrichment
  52. 2026-06-06 15:14 UTCEG score recompute
  53. 2026-06-06 15:14 UTCVendor advisory
  54. 2026-06-06 15:13 UTCGHSA enrichment
  55. 2026-06-06 13:47 UTCEPSS rescore
  56. 2026-06-06 13:47 UTCEPSS rescore
  57. 2026-06-06 02:46 UTCEG score recompute
  58. 2026-06-06 02:46 UTCVendor advisory
  59. 2026-06-06 02:46 UTCGHSA enrichment
  60. 2026-06-05 22:47 UTCEPSS rescore
  61. 2026-06-05 22:47 UTCEPSS rescore
  62. 2026-06-05 14:06 UTCEG score recompute
  63. 2026-06-05 14:06 UTCVendor advisory
  64. 2026-06-05 14:06 UTCGHSA enrichment
  65. 2026-06-05 06:10 UTCEPSS rescore
  66. 2026-06-05 06:10 UTCEPSS rescore
  67. 2026-06-05 01:42 UTCEG score recompute
  68. 2026-06-05 01:42 UTCVendor advisory
  69. 2026-06-05 01:42 UTCGHSA enrichment
  70. 2026-06-04 13:12 UTCEPSS rescore
  71. 2026-06-04 13:12 UTCEPSS rescore
  72. 2026-06-04 12:56 UTCEG score recompute
  73. 2026-06-04 12:56 UTCVendor advisory
  74. 2026-06-04 12:56 UTCGHSA enrichment
  75. 2026-06-04 00:31 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-31700?
CVE-2026-31700 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: net/packet: fix TOCTOU race on mmap'd vnethdr in tpacketsnd() In tpacketsnd(), when PACKETVNETHDR is enabled, vnethdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via…
When was CVE-2026-31700 disclosed?
CVE-2026-31700 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31700 actively exploited?
CVE-2026-31700 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31700?
CVE-2026-31700 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31700?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31700, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-31700

Explore →

Is Your Infrastructure Affected by CVE-2026-31700?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.