Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update

HighCVSS 7.8 · v3.1—No exploit Fix available

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.17% (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 172dcb67dd35b162357df229d7806acc724cd469, 2889d92c5f728351c9930c7996d22fe6e906e785, bd25b092a06a3e05f7e8bd6da6fa7318777d8c3d; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 172dcb67dd35b162357df229d7806acc724cd469, 2889d92c5f728351c9930c7996d22fe6e906e785, bd25b092a06a3e05f7e8bd6da6fa7318777d8c3d; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: bonding: fix use-after-free due to enslave fail after slave array update Fix a use-after-free which happens due to enslave failure after the new slave has been added to the array. Since the new slave can be used for Tx immediately, we can use it after it has been freed by the enslave error cleanup path which frees the allocated slave memory. Slave update array is supposed to be called last when further enslave failures are not expected. Move it after xdp setup to avoid any problems. It is very easy to reproduce the problem with a simple xdp_pass prog: ip l add bond1 type bond mode balance-xor ip l set bond1 up ip l set dev bond1 xdp object xdp_pass.o sec xdp_pass ip l add dumdum type dummy Then run in parallel: while :; do ip l set dumdum master bond1 1>/dev/null 2>&1; done; mausezahn bond1 -a own -b rand -A rand -B 1.1.1.1 -c 0 -t tcp "dp=1-1023, flags=syn" The crash happens almost immediately: [ 605.602850] Oops: general protection fault, probably for non-canonical address 0xe0e6fc2460000137: 0000 [#1] SMP KASAN NOPTI [ 605.602916] KASAN: maybe wild-memory-access in range [0x07380123000009b8-0x07380123000009bf] [ 605.602946] CPU: 0 UID: 0 PID: 2445 Comm: mausezahn Kdump: loaded Tainted: G B 6.19.0-rc6+ #21 PREEMPT(voluntary) [ 605.602979] Tainted: [B]=BAD_PAGE [ 605.602998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 605.603032] RIP: 0010:netdev_core_pick_tx+0xcd/0x210 [ 605.603063] Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3e 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 6b 08 49 8d 7d 30 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 25 01 00 00 49 8b 45 30 4c 89 e2 48 89 ee 48 89 [ 605.603111] RSP: 0018:ffff88817b9af348 EFLAGS: 00010213 [ 605.603145] RAX: dffffc0000000000 RBX: ffff88817d28b420 RCX: 0000000000000000 [ 605.603172] RDX: 00e7002460000137 RSI: 0000000000000008 RDI: 07380123000009be [ 605.603199] RBP: ffff88817b541a00 R08: 0000000000000001 R09: fffffbfff3ed8c0c [ 605.603226] R10: ffffffff9f6c6067 R11: 0000000000000001 R12: 0000000000000000 [ 605.603253] R13: 073801230000098e R14: ffff88817d28b448 R15: ffff88817b541a84 [ 605.603286] FS: 00007f6570ef67c0(0000) GS:ffff888221dfa000(0000) knlGS:0000000000000000 [ 605.603319] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 605.603343] CR2: 00007f65712fae40 CR3: 000000011371b000 CR4: 0000000000350ef0 [ 605.603373] Call Trace: [ 605.603392] <TASK> [ 605.603410] __dev_queue_xmit+0x448/0x32a0 [ 605.603434] ? __pfx_vprintk_emit+0x10/0x10 [ 605.603461] ? __pfx_vprintk_emit+0x10/0x10 [ 605.603484] ? __pfx___dev_queue_xmit+0x10/0x10 [ 605.603507] ? bond_start_xmit+0xbfb/0xc20 [bonding] [ 605.603546] ? _printk+0xcb/0x100 [ 605.603566] ? __pfx__printk+0x10/0x10 [ 605.603589] ? bond_start_xmit+0xbfb/0xc20 [bonding] [ 605.603627] ? add_taint+0x5e/0x70 [ 605.603648] ? add_taint+0x2a/0x70 [ 605.603670] ? end_report.cold+0x51/0x75 [ 605.603693] ? bond_start_xmit+0xbfb/0xc20 [bonding] [ 605.603731] bond_start_xmit+0x623/0xc20 [bonding]

Published
Feb 14, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 6th 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
7.8
CNA · Linux
7.8
agree

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-23171

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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.

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

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

    • 5.15affected
    • 9e2ee5c7e7c35d195e2aa0692a7241d47a433d1e and later · before c6ae2b978001065ca0e1d33d5cbf949efeff879eaffected · git
    • 9e2ee5c7e7c35d195e2aa0692a7241d47a433d1e and later · before 172dcb67dd35b162357df229d7806acc724cd469affected · git
    • 9e2ee5c7e7c35d195e2aa0692a7241d47a433d1e and later · before 2889d92c5f728351c9930c7996d22fe6e906e785affected · git
    • 9e2ee5c7e7c35d195e2aa0692a7241d47a433d1e and later · before bd25b092a06a3e05f7e8bd6da6fa7318777d8c3daffected · git
    • 9e2ee5c7e7c35d195e2aa0692a7241d47a433d1e and later · before e9acda52fd2ee0cdca332f996da7a95c5fd25294affected · git
    • before 5.15not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.140 and later · up to and including 6.6.*not affected · semver
    • 6.12.90 and later · up to and including 6.12.*not affected · semver

Affected versions

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

  • linux linux kernel5.15 and later · before 6.18.9
  • linux linux kernel6.19

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.49.1.el10_16.12.0-124.49.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.49.1.el10_16.12.0-124.49.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.45.1.el9_75.14.0-611.45.1.el9_7

+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-23164Feb 14, 2026 · rocker: fix memory leak in rocker_world_port_post_fini()
    22Monitor
  • ← EarlierCVE-2026-23166Feb 14, 2026 · ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues
    22Monitor
  • Later →CVE-2026-23172Feb 14, 2026 · net: wwan: t7xx: fix potential skb->frags overflow in RX path
    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 Linux172dcb67dd35b162357df229d7806acc724cd469Vendor (CNA)
Linux Linux2889d92c5f728351c9930c7996d22fe6e906e785Vendor (CNA)
Linux Linuxbd25b092a06a3e05f7e8bd6da6fa7318777d8c3dVendor (CNA)
Linux Linuxc6ae2b978001065ca0e1d33d5cbf949efeff879eVendor (CNA)
Linux Linuxe9acda52fd2ee0cdca332f996da7a95c5fd25294Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.45.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.90-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

+2

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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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-primary

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.

References

All records