CVE-2024-46678: bonding: change ipsec_lock from spin lock to mutex
bonding: change ipseclock from spin lock to mutex
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.22-1Fixed in 6.12.25-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.51.1-5 - Configuration
Change bonding ipsec_lock from a spin lock to a mutex (bonding: change ipsec_lock from spin lock to mutex) to prevent "scheduling while atomic" when calling xdo_dev_state_add/xdo_dev_state_delete inside the lock.
Linux kernel bonding (bonding.ko) bond->ipsec_lock lock type = mutex
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46678?
The severity of CVE-2024-46678 is determined by its impact on system security and stability, requiring careful evaluation.
How do I fix CVE-2024-46678?
To fix CVE-2024-46678, update your Linux kernel to a version that addresses this vulnerability, such as 6.12.12-1 or later.
Which Linux kernel versions are affected by CVE-2024-46678?
CVE-2024-46678 affects Linux kernel versions between 5.10.54 to 5.14 and various subsequent versions up to 6.11-rc5.
What components are involved in CVE-2024-46678?
CVE-2024-46678 involves the bonding driver and ipsec_lock mechanism within the Linux kernel.
Is CVE-2024-46678 a local or remote vulnerability?
CVE-2024-46678 is a local vulnerability requiring access to the affected system to exploit.