Skip to content
major vulnerability· requires attention

Affects core Linux kernel; widely deployed and critical infrastructure; potential memory disclosure via crafted IPv6 ND options.

Networks

CVE-2026-31682

9.1
Critical
EPSS 0.48%Patch availableApr 28, 2026

Linux kernel ND option parsing may read non-linear data.

common questions

Is CVE-2026-31682 being exploited?

Not confirmed. CVE-2026-31682 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.

How severe is CVE-2026-31682?

CVE-2026-31682 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-31682?

Yes. A fix has been recorded for CVE-2026-31682. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-31682 affect?

CVE-2026-31682 affects Linux kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-31682?

Update to patched kernel version and reboot

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel
impact

Remote memory disclosure and potential DoS via crafted IPv6 ND messages triggering br_nd_send parsing.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < c68433fd291c9e88c00292095172c62d1997d662
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < 4f397b950c916e9a1f8a4fce04ea0110206cad47
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < bd91ec85aa4c77d645bd2739fc56784157a88ca2
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < 658261898130da620fc3d0fbb0523efb3366cb55
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < 2ba4caba423ed94d63006eb1d2227b0332ab7fcd
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < 9c55e41c73af5c4511070933b1bd25248521270c
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < 3a30f6469b058574f49efde61cd6f5d79e576053
  • affected>= ed842faeb2bd49256f00485402f3113205f91d30 and < a01aee7cafc575bb82f5529e8734e7052f9b16ea
  • affected4.15
vendor says fixed in< 4.15, >= 5.10.253 and <= 5.10.*, >= 5.15.203 and <= 5.15.*, >= 6.1.168 and <= 6.1.*, >= 6.6.134 and <= 6.6.*, >= 6.12.81 and <= 6.12.*, >= 6.18.22 and <= 6.18.*, >= 6.19.12 and <= 6.19.*, >= 7.0 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free