Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 00752893f96b344f258c9c6de18b33171ac4872c, 060d83bb6147c36fc21134d5b332d266b8c176bc, 2884bf72fb8f03409e423397319205de48adca16.

Low priority for now. Upgrade to Linux Linux 00752893f96b344f258c9c6de18b33171ac4872c, 060d83bb6147c36fc21134d5b332d266b8c176bc, 2884bf72fb8f03409e423397319205de48adca16 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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: <TASK> 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) </TASK> 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 ==================================================================

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 13, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31419

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.10.94 and later · before 5.11
  • linux linux kernel5.15.17 and later · before 5.16
  • linux linux kernel5.16.3 and later · before 5.17
  • linux linux kernel5.17 and later · before 6.12.86
  • linux linux kernel6.13 and later · before 6.18.22
  • linux linux kernel6.19 and later · before 6.19.12
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • c1f1691ef84fa6d38fa5e5148eca073145e97ffa, 5.17affected
    • 20949c3816463e97c6f8fe84c0280c7e5ae83a8d and later · before 060d83bb6147c36fc21134d5b332d266b8c176bcaffected · git
    • f1d206181f19b00b275b258fea1418718a2f4173 and later · before df690112b2172e8eb0f4dd8ec1019b65ee979203affected · git
    • 4e5bd03ae34652cd932ab4c91c71c511793df75c and later · before 00752893f96b344f258c9c6de18b33171ac4872caffected · git
    • 4e5bd03ae34652cd932ab4c91c71c511793df75c and later · before 2de5c8eea0a9db99dae7c36f4b541b74b41d3a04affected · git
    • 4e5bd03ae34652cd932ab4c91c71c511793df75c and later · before a0f661918edc79d7a75e468128af8d41e2a1a83aaffected · git
    • 4e5bd03ae34652cd932ab4c91c71c511793df75c and later · before d4cc7e4c80b1634c7b1497574a2fdb18df6c026caffected · git
    • 4e5bd03ae34652cd932ab4c91c71c511793df75c and later · before f5b94654a4a19891a8108d66ef166de6c028c6cdaffected · git
    • 4e5bd03ae34652cd932ab4c91c71c511793df75c and later · before 2884bf72fb8f03409e423397319205de48adca16affected · git
    • 5.10.94 and later · before 5.10.273affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.55.1.el10_16.12.0-124.55.1.el10_1
AlmaLinux:10kernel-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31417Apr 13, 2026 · net/x25: Fix overflow when accumulating packets
    30Monitor
  • ← EarlierCVE-2026-31418Apr 13, 2026 · netfilter: ipset: drop logically empty buckets in mtype_del
    22Monitor
  • Later →CVE-2026-31421Apr 13, 2026 · net/sched: cls_fw: fix NULL pointer dereference on shared blocks
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux00752893f96b344f258c9c6de18b33171ac4872cVendor (CNA)
Linux Linux060d83bb6147c36fc21134d5b332d266b8c176bcVendor (CNA)
Linux Linux2884bf72fb8f03409e423397319205de48adca16Vendor (CNA)
Linux Linux2de5c8eea0a9db99dae7c36f4b541b74b41d3a04Vendor (CNA)
Linux Linux5.10.273Vendor (CNA)
Linux Linux5.15.224Vendor (CNA)
Linux Linux5.17Vendor (CNA)
Linux Linuxa0f661918edc79d7a75e468128af8d41e2a1a83aVendor (CNA)
Linux Linuxd4cc7e4c80b1634c7b1497574a2fdb18df6c026cVendor (CNA)
Linux Linuxdf690112b2172e8eb0f4dd8ec1019b65ee979203Vendor (CNA)
Linux Linuxf5b94654a4a19891a8108d66ef166de6c028c6cdVendor (CNA)
almalinux:kernel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.22.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-124.55.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-124.55.1.el10_1 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-124.55.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-124.55.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-124.55.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-124.55.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-124.55.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-124.55.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)

+8

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records