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

August 5, 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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 31× 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 260 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 August 5, 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.4% 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

See which npm, PyPI, Go, and Maven packages are affected by 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