CVE-2026-31682

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-25. the CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: 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:

bridge: br_nd_send: linearize skb before parsing ND options

br_nd_send() parses neighbour discovery options from ns->opt[] and assumes that these options are in the linear part of request.

Its callers only guarantee that the ICMPv6 header and target address are available, so the option area can still be non-linear. Parsing ns->opt[] in that case can access data past the linear buffer.

Linearize request before option parsing and derive ns from the linear network header.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

April 25, 2026

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c55e41c73af5c4511070933b1bd25248521270c
generic

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/658261898130da620fc3d0fbb0523efb3366cb55
generic

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: br_nd_send: linearize skb before parsing ND options - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c68433fd291c9e88c00292095172c62d1997d662
generic🔴 Active Exploitation

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
generic

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html

Vendor Advisories for CVE-2026-31682(2)

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 @ 5.10.253—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

(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.12-1—

Additional Vendor Advisories

(24)

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 8× in last 7d / 116× 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 402 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31682?
CVE-2026-31682 is a critical vulnerability published on April 25, 2026. In the Linux kernel, the following vulnerability has been resolved: bridge: brndsend: linearize skb before parsing ND options brndsend() parses neighbour discovery options from ns->opt[] and assumes that these options are in the linear part of request. Its callers only guarantee that the ICMPv6…
When was CVE-2026-31682 disclosed?
CVE-2026-31682 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-31682 actively exploited?
CVE-2026-31682 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 60.0% of all scored CVEs.
What is the CVSS score of CVE-2026-31682?
CVE-2026-31682 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31682?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31682, 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-31682

Explore →

Is Your Infrastructure Affected by CVE-2026-31682?

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

Start Free Scan →Browse All CVEs