Linux kernel bonding type confusion in bond_setup_by_slave()
CVE-2026-43456 is a Linux kernel vulnerability in the bonding driver caused by type confusion in bond_setup_by_slave(). When a non-Ethernet slave device such as a GRE tunnel is enslaved to a bond interface, the bonding code copies the slave device's header_ops directly into the bond device. Later, when dev_hard_header() invokes callbacks such as ipgre_header() or ip6gre_header() through those inherited header_ops, the callback executes in the context of the bond device rather than the original slave device. Those header functions use netdev_priv(dev) and therefore interpret the bond device's private data (struct bonding) as if it were the slave driver's expected private structure (for example struct ip_tunnel). This results in invalid memory interpretation, garbage values, and kernel crashes, as evidenced by the reported BUG in pskb_expand_head(). The upstream fix introduces bond_header_ops wrapper functions that dispatch to the active slave's header_ops using the slave device itself, ensuring netdev_priv() resolves to the correct private data layout.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.