CVE-2026-31683

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:

batman-adv: avoid OGM aggregation when skb tailroom is insufficient

When OGM aggregation state is toggled at runtime, an existing forwarded packet may have been allocated with only packet_len bytes, while a later packet can still be selected for aggregation. Appending in this case can hit skb_put overflow conditions.

Reject aggregation when the target skb tailroom cannot accommodate the new packet. The caller then falls back to creating a new forward packet instead of appending.

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
2%
KEV
Not listed

Published

April 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

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

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e40ebb999c2c3d2fbb3cacb61f0384ee6e69075
generic

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6755347c5f9bdd44dee80f692208b056fcd40a52
generic

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67176c96f325837b0bb3e9538ca2eba414f447d8
generic

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ada20331f2df2a942d6b83ae1f04a304b642e2a
generic

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e35db29fc5a97a8553f7c2d3a2ba730e46b1ee8
generic

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d4aef630be9d5f9c1227d07669c26c4383b5ad0
generic

batman-adv: avoid OGM aggregation when skb tailroom is insufficient - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b10a8b355c3f71012ce89289ec2c2f5e3bfd6c1

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
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 (122 versions)6.19.10-1

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 32× 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 233 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31683?
CVE-2026-31683 is a high vulnerability published on April 25, 2026. In the Linux kernel, the following vulnerability has been resolved: batman-adv: avoid OGM aggregation when skb tailroom is insufficient When OGM aggregation state is toggled at runtime, an existing forwarded packet may have been allocated with only packet_len bytes, while a later packet can still…
When was CVE-2026-31683 disclosed?
CVE-2026-31683 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-31683 actively exploited?
CVE-2026-31683 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31683?
CVE-2026-31683 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31683?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31683, 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-31683

Explore →

Is Your Infrastructure Affected by CVE-2026-31683?

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