Kernel memory corruption via ALB teardown race
Published May 27, 2026 · Updated May 27, 2026
Use-after-free in Linux Kernel's ALB bonding receive path allows local users to corrupt kernel memory or crash the system during bond teardown. rlb_deinitialize() frees rx_hashtbl while rlb_arp_recv() can remain active, so a concurrent ARP receive handler dereferences and writes through reclaimed heap memory. A low-privileged local user can control both sides of the race in a user and network namespace by injecting ARP frames while cycling a balance-alb bond up and down, with no victim interaction.
Summary
What happened
Use-after-free in Linux Kernel's ALB bonding receive path allows local users to corrupt kernel memory or crash the system during bond teardown. rlb_deinitialize() frees rx_hashtbl while rlb_arp_recv() can remain active, so a concurrent ARP receive handler dereferences and writes through reclaimed heap memory. A low-privileged local user can control both sides of the race in a user and network namespace by injecting ARP frames while cycling a balance-alb bond up and down, with no victim interaction.
The record
- CVE
- CVE-2026-45970
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <c65cdf46ce340c9c00fbbaf84599d2daff43626e
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <d31065526f160ee0244a719230aa069daca2bf4d
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <db5435b5342e3aaa4521d0f3ccfe94316b253ca1
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <de7c097800f07f3c108185c7a38b53a530ba30ff
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <e6834a4c474697df23ab9948fd3577b26bf48656
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <f94a0de7b9f32745a14a1621c63087a092823587
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <fd54ddc929be1d6c3b3b7b35d6d4642a5d9e803c
- Affected versionversion=3aba891dde3842d89ad022237b99c1ed308040b0 <fef13c403be3fb685cb06419e6b3623106aab5ba
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo