CVE-2026-31419

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-13. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: bonding: fix use-after-free in bond_xmit_broadcast()

bond_xmit_broadcast() reuses the original skb for the last slave (determined by bond_is_last_slave()) and clones it for others. Concurrent slave enslave/release can mutate the slave list during RCU-protected iteration, changing which slave is "last" mid-loop. This causes the original skb to be double-consumed (double-freed).

Replace the racy bond_is_last_slave() check with a simple index comparison (i + 1 == slaves_count) against the pre-snapshot slave count taken via READ_ONCE() before the loop. This preserves the zero-copy optimization for the last slave while making the "last" determination stable against concurrent list mutations.

The UAF can trigger the following crash:

================================================================== BUG: KASAN: slab-use-after-free in skb_clone Read of size 8 at addr ffff888100ef8d40 by task exploit/147

CPU: 1 UID: 0 PID: 147 Comm: exploit Not tainted 7.0.0-rc3+ #4 PREEMPTLAZY Call Trace: dump_stack_lvl (lib/dump_stack.c:123) print_report (mm/kasan/report.c:379 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:597) skb_clone (include/linux/skbuff.h:1724 include/linux/skbuff.h:1792 include/linux/skbuff.h:3396 net/core/skbuff.c:2108) bond_xmit_broadcast (drivers/net/bonding/bond_main.c:5334) bond_start_xmit (drivers/net/bonding/bond_main.c:5567 drivers/net/bonding/bond_main.c:5593) dev_hard_start_xmit (include/linux/netdevice.h:5325 include/linux/netdevice.h:5334 net/core/dev.c:3871 net/core/dev.c:3887) __dev_queue_xmit (include/linux/netdevice.h:3601 net/core/dev.c:4838) ip6_finish_output2 (include/net/neighbour.h:540 include/net/neighbour.h:554 net/ipv6/ip6_output.c:136) ip6_finish_output (net/ipv6/ip6_output.c:208 net/ipv6/ip6_output.c:219) ip6_output (net/ipv6/ip6_output.c:250) ip6_send_skb (net/ipv6/ip6_output.c:1985) udp_v6_send_skb (net/ipv6/udp.c:1442) udpv6_sendmsg (net/ipv6/udp.c:1733) __sys_sendto (net/socket.c:730 net/socket.c:742 net/socket.c:2206) __x64_sys_sendto (net/socket.c:2209) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)

Allocated by task 147:

Freed by task 147:

The buggy address belongs to the object at ffff888100ef8c80 which belongs to the cache skbuff_head_cache of size 224 The buggy address is located 192 bytes inside of freed 224-byte region [ffff888100ef8c80, ffff888100ef8d60)

Memory state around the buggy address: ffff888100ef8c00: fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc ffff888100ef8c80: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff888100ef8d00: fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ^ ffff888100ef8d80: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb ffff888100ef8e00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================

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 13, 2026

Last Modified

August 23, 2026

Advisory Details (4)

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

net: bonding: fix use-after-free in bond_xmit_broadcast() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: bonding: fix use-after-free in bond_xmit_broadcast() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: bonding: fix use-after-free in bond_xmit_broadcast() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3453882f36c40d2339267093676585a89808a73d
generic

net: bonding: fix use-after-free in bond_xmit_broadcast() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2884bf72fb8f03409e423397319205de48adca16

Vendor Advisories for CVE-2026-31419(18)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.179.189~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1049.51) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1015.15) @ questing2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1025.25) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.179.151) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1018.19) @ questing2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1114.99) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1114.112) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-08-23ubuntu
redhatkpatch-patch2026-07-08redhat
redhatkernel-0:4.18.0-553.136.1.el8_102026-06-19redhat
redhatkernel-rt-0:4.18.0-553.136.1.rt7.477.el8_102026-06-19redhat
redhatkernel-0:6.12.0-211.22.1.el10_22026-06-11redhat
redhatkernel-0:5.14.0-687.15.1.el9_82026-06-11redhat
redhatkernel-0:5.14.0-570.119.1.el9_62026-06-04redhat
redhatkernel-0:5.14.0-284.174.1.el9_22026-06-03redhat
redhatkernel-rt-0:5.14.0-284.174.1.rt14.459.el9_22026-06-03redhat
redhatkernel-0:6.12.0-55.76.1.el10_02026-06-01redhat
redhatkernel-0:5.14.0-427.127.1.el9_42026-05-27redhat
redhatkernel-0:4.18.0-477.143.1.el8_82026-05-20redhat
redhatkernel-0:6.12.0-124.55.1.el10_12026-05-04redhat
linuxKernel @ 6.6.143—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~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.12-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

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 6× in last 7d / 82× 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 220 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-31419?
CVE-2026-31419 is a high vulnerability published on April 13, 2026. In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix use-after-free in bondxmitbroadcast() bondxmitbroadcast() reuses the original skb for the last slave (determined by bondislast_slave()) and clones it for others. Concurrent slave enslave/release can mutate the…
When was CVE-2026-31419 disclosed?
CVE-2026-31419 was first published in the National Vulnerability Database on April 13, 2026, with the most recent update on August 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31419 actively exploited?
CVE-2026-31419 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-31419?
CVE-2026-31419 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31419, 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-31419

Explore →

Is Your Infrastructure Affected by CVE-2026-31419?

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

Start Free Scan →Browse All CVEs