Service interruption via lockless bonding state access
Published Feb 18, 2026 · Updated Feb 18, 2026
A data race in the Linux kernel bonding driver allows local users to interrupt service through concurrent packet processing. The bond_rcv_validate path reads and writes slave->last_rx and slave->target_last_arp_rx elements without single-access synchronization, allowing interrupt handlers on different CPUs to access the same state concurrently. Exploitation requires local low-privileged access, a configured bonding interface, and favorable timing; the public record does not identify whether interruption manifests as a hang, crash, or reboot.
Summary
What happened
A data race in the Linux kernel bonding driver allows local users to interrupt service through concurrent packet processing. The bond_rcv_validate path reads and writes slave->last_rx and slave->target_last_arp_rx elements without single-access synchronization, allowing interrupt handlers on different CPUs to access the same state concurrently. Exploitation requires local low-privileged access, a configured bonding interface, and favorable timing; the public record does not identify whether interruption manifests as a hang, crash, or reboot.
The record
- CVE
- CVE-2026-23212
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-367, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 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=2.6.19
- Affected versionversion=f5b2b966f032f22d3a289045a5afd4afa09f09c6 <8c0be3277e7aefb2f900fc37ca3fe7df362e26f5
- Affected versionversion=f5b2b966f032f22d3a289045a5afd4afa09f09c6 <a7516cb0165926d308187e231ccd330e5e3ebff7
- Affected versionversion=f5b2b966f032f22d3a289045a5afd4afa09f09c6 <b956289b83887e0a306067b6003c3fcd81bfdf84
- Affected versionversion=f5b2b966f032f22d3a289045a5afd4afa09f09c6 <bd98324e327e41de04b13e372cc16f73150df254
- Affected versionversion=f5b2b966f032f22d3a289045a5afd4afa09f09c6 <f6c3665b6dc53c3ab7d31b585446a953a74340ef
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.
Weakness, pattern, technique
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