Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-45970: bonding: alb: fix UAF in rlb_arp_recv during bond up/down

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 c65cdf46ce340c9c00fbbaf84599d2daff43626e, d31065526f160ee0244a719230aa069daca2bf4d, db5435b5342e3aaa4521d0f3ccfe94316b253ca1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux c65cdf46ce340c9c00fbbaf84599d2daff43626e, d31065526f160ee0244a719230aa069daca2bf4d, db5435b5342e3aaa4521d0f3ccfe94316b253ca1 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: alb: fix UAF in rlb_arp_recv during bond up/down The ALB RX path may access rx_hashtbl concurrently with bond teardown. During rapid bond up/down cycles, rlb_deinitialize() frees rx_hashtbl while RX handlers are still running, leading to a null pointer dereference detected by KASAN. However, the root cause is that rlb_arp_recv() can still be accessed after setting recv_probe to NULL, which is actually a use-after-free (UAF) issue. That is the reason for using the referenced commit in the Fixes tag. [ 214.174138] Oops: general protection fault, probably for non-canonical address 0xdffffc000000001d: 0000 [#1] SMP KASAN PTI [ 214.186478] KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef] [ 214.194933] CPU: 30 UID: 0 PID: 2375 Comm: ping Kdump: loaded Not tainted 6.19.0-rc8+ #2 PREEMPT(voluntary) [ 214.205907] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.14.0 01/14/2022 [ 214.214357] RIP: 0010:rlb_arp_recv+0x505/0xab0 [bonding] [ 214.220320] Code: 0f 85 2b 05 00 00 48 b8 00 00 00 00 00 fc ff df 40 0f b6 ed 48 c1 e5 06 49 03 ad 78 01 00 00 48 8d 7d 28 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 06 0f 8e 12 05 00 00 80 7d 28 00 0f 84 8c 00 [ 214.241280] RSP: 0018:ffffc900073d8870 EFLAGS: 00010206 [ 214.247116] RAX: dffffc0000000000 RBX: ffff888168556822 RCX: ffff88816855681e [ 214.255082] RDX: 000000000000001d RSI: dffffc0000000000 RDI: 00000000000000e8 [ 214.263048] RBP: 00000000000000c0 R08: 0000000000000002 R09: ffffed11192021c8 [ 214.271013] R10: ffff8888c9010e43 R11: 0000000000000001 R12: 1ffff92000e7b119 [ 214.278978] R13: ffff8888c9010e00 R14: ffff888168556822 R15: ffff888168556810 [ 214.286943] FS: 00007f85d2d9cb80(0000) GS:ffff88886ccb3000(0000) knlGS:0000000000000000 [ 214.295966] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 214.302380] CR2: 00007f0d047b5e34 CR3: 00000008a1c2e002 CR4: 00000000001726f0 [ 214.310347] Call Trace: [ 214.313070] <IRQ> [ 214.315318] ? __pfx_rlb_arp_recv+0x10/0x10 [bonding] [ 214.320975] bond_handle_frame+0x166/0xb60 [bonding] [ 214.326537] ? __pfx_bond_handle_frame+0x10/0x10 [bonding] [ 214.332680] __netif_receive_skb_core.constprop.0+0x576/0x2710 [ 214.339199] ? __pfx_arp_process+0x10/0x10 [ 214.343775] ? sched_balance_find_src_group+0x98/0x630 [ 214.349513] ? __pfx___netif_receive_skb_core.constprop.0+0x10/0x10 [ 214.356513] ? arp_rcv+0x307/0x690 [ 214.360311] ? __pfx_arp_rcv+0x10/0x10 [ 214.364499] ? __lock_acquire+0x58c/0xbd0 [ 214.368975] __netif_receive_skb_one_core+0xae/0x1b0 [ 214.374518] ? __pfx___netif_receive_skb_one_core+0x10/0x10 [ 214.380743] ? lock_acquire+0x10b/0x140 [ 214.385026] process_backlog+0x3f1/0x13a0 [ 214.389502] ? process_backlog+0x3aa/0x13a0 [ 214.394174] __napi_poll.constprop.0+0x9f/0x370 [ 214.399233] net_rx_action+0x8c1/0xe60 [ 214.403423] ? __pfx_net_rx_action+0x10/0x10 [ 214.408193] ? lock_acquire.part.0+0xbd/0x260 [ 214.413058] ? sched_clock_cpu+0x6c/0x540 [ 214.417540] ? mark_held_locks+0x40/0x70 [ 214.421920] handle_softirqs+0x1fd/0x860 [ 214.426302] ? __pfx_handle_softirqs+0x10/0x10 [ 214.431264] ? __neigh_event_send+0x2d6/0xf50 [ 214.436131] do_softirq+0xb1/0xf0 [ 214.439830] </IRQ> The issue is reproducible by repeatedly running ip link set bond0 up/down while receiving ARP messages, where rlb_arp_recv() can race with rlb_deinitialize() and dereference a freed rx_hashtbl entry. Fix this by setting recv_probe to NULL and then calling synchronize_net() to wait for any concurrent RX processing to finish. This ensures that no RX handler can access rx_hashtbl after it is freed in bond_alb_deinitialize().

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Oct 19, 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-45970

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 kernel3.0 and later · before 5.10.252
  • linux linux kernel5.11 and later · before 5.15.202
  • linux linux kernel5.16 and later · before 6.1.165
  • linux linux kernel6.2 and later · before 6.6.128
  • linux linux kernel6.7 and later · before 6.12.75
  • linux linux kernel6.13 and later · before 6.18.14
  • linux linux kernel6.19 and later · before 6.19.4

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

    • 3.0affected
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before fd54ddc929be1d6c3b3b7b35d6d4642a5d9e803caffected · git
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before de7c097800f07f3c108185c7a38b53a530ba30ffaffected · git
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before db5435b5342e3aaa4521d0f3ccfe94316b253ca1affected · git
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before f94a0de7b9f32745a14a1621c63087a092823587affected · git
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before c65cdf46ce340c9c00fbbaf84599d2daff43626eaffected · git
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before fef13c403be3fb685cb06419e6b3623106aab5baaffected · git
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before d31065526f160ee0244a719230aa069daca2bf4daffected · git
    • 3aba891dde3842d89ad022237b99c1ed308040b0 and later · before e6834a4c474697df23ab9948fd3577b26bf48656affected · git
    • before 3.0not affected · 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.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.50.1.el10_26.12.0-211.50.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.50.1.el10_26.12.0-211.50.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-45959May 27, 2026 · crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree
    31Monitor
  • ← EarlierCVE-2026-45961May 27, 2026 · gfs2: fix memory leaks in gfs2_fill_super error path
    22Monitor
  • Later →CVE-2026-45972May 27, 2026 · smb: client: fix potential UAF and double free in smb2_open_file()
    39Monitor

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 Linuxc65cdf46ce340c9c00fbbaf84599d2daff43626eVendor (CNA)
Linux Linuxd31065526f160ee0244a719230aa069daca2bf4dVendor (CNA)
Linux Linuxdb5435b5342e3aaa4521d0f3ccfe94316b253ca1Vendor (CNA)
Linux Linuxde7c097800f07f3c108185c7a38b53a530ba30ffVendor (CNA)
Linux Linuxe6834a4c474697df23ab9948fd3577b26bf48656Vendor (CNA)
Linux Linuxf94a0de7b9f32745a14a1621c63087a092823587Vendor (CNA)
Linux Linuxfd54ddc929be1d6c3b3b7b35d6d4642a5d9e803cVendor (CNA)
Linux Linuxfef13c403be3fb685cb06419e6b3623106aab5baVendor (CNA)
almalinux:kernel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.50.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+17

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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