CVE-2026-52975: bonding: 3ad: implement proper RCU rules for port->aggregator
bonding: 3ad: implement proper RCU rules for port->aggregator
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1 - Configuration
Update drivers/net/bonding/bond_3ad.c: add the __rcu qualifier to port->aggregator and implement proper RCU rules for any concurrent access in bond_3ad_get_active_agg_info and bond_3ad_state_machine_handler, using the appropriate RCU API (as indicated by the resolved issue: 'implement proper RCU rules for port->aggregator').
Linux kernel bonding (bond_3ad) port->aggregator RCU usage = Add __rcu qualifier and use proper RCU API for port->aggregator accesses (to satisfy RCU read-side rules)
Event History
Frequently Asked Questions
What is the severity of CVE-2026-52975?
CVE-2026-52975 has a risk score of 27 indicating a moderate level of severity.
How do I fix CVE-2026-52975?
To fix CVE-2026-52975, ensure that you update your Linux kernel to the latest version that includes the patch addressing this vulnerability.
What systems are affected by CVE-2026-52975?
CVE-2026-52975 affects the Linux kernel specifically within the bonding driver.
What type of vulnerability is CVE-2026-52975?
CVE-2026-52975 is a data race vulnerability caused by improper RCU rules implementation.
How can I check if my Linux kernel is vulnerable to CVE-2026-52975?
You can check your Linux kernel version against the versions listed in the advisory to determine if it's vulnerable to CVE-2026-52975.