CVE-2026-31675

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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/sched: sch_netem: fix out-of-bounds access in packet corruption

In netem_enqueue(), the packet corruption logic uses get_random_u32_below(skb_headlen(skb)) to select an index for modifying skb->data. When an AF_PACKET TX_RING sends fully non-linear packets over an IPIP tunnel, skb_headlen(skb) evaluates to 0.

Passing 0 to get_random_u32_below() takes the variable-ceil slow path which returns an unconstrained 32-bit random integer. Using this unconstrained value as an offset into skb->data results in an out-of-bounds memory access.

Fix this by verifying skb_headlen(skb) is non-zero before attempting to corrupt the linear data area. Fully non-linear packets will silently bypass the corruption logic.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 25, 2026

Last Modified

May 6, 2026

Advisory Details (5)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

net/sched: sch_netem: fix out-of-bounds access in packet corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d64cb81dcbd54927515a7f65e5e24affdc73c14b
generic

net/sched: sch_netem: fix out-of-bounds access in packet corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a14b56863348686dd0387eea8ce66b85cf455908
generic

net/sched: sch_netem: fix out-of-bounds access in packet corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fd258e281fa8bc15e9ce2c7691941537e9258ad
generic

net/sched: sch_netem: fix out-of-bounds access in packet corruption - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: sch_netem: fix out-of-bounds access in packet corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13a66ca1e235d4bcd53d12d4c68490cad7f8e46f

Vendor Advisories for CVE-2026-31675(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.6.134—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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 159 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31675?
CVE-2026-31675 is a high vulnerability published on April 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_netem: fix out-of-bounds access in packet corruption In netem_enqueue(), the packet corruption logic uses getrandomu32below(skbheadlen(skb)) to select an index for modifying skb->data. When an AFPACKET TXRING sends…
When was CVE-2026-31675 disclosed?
CVE-2026-31675 was first published in the National Vulnerability Database on April 25, 2026, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31675 actively exploited?
CVE-2026-31675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31675?
CVE-2026-31675 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31675, 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-31675

Explore →

Is Your Infrastructure Affected by CVE-2026-31675?

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

Start Free Scan →Browse All CVEs