# CVE-2024-46678: bonding: change ipsec_lock from spin lock to mutex CVE-2024-46678 is fixed in 26 products on 1 platform, first by DEBIAN-CVE-2024-46678, released September 13, 2024. It is not reported as exploited. Patch Radar priority: Routine. - Web page: https://patchblox.com/security/cve/CVE-2024-46678 - Priority: Routine - CVSS: 5.5 (Moderate) - EPSS: 0.0017 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Sep 13, 2024 - Weakness: Improper Locking - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-46678 ## Description In the Linux kernel, the following vulnerability has been resolved: bonding: change ipsec_lock from spin lock to mutex In the cited commit, bond->ipsec_lock is added to protect ipsec_list, hence xdo_dev_state_add and xdo_dev_state_delete are called inside this lock. As ipsec_lock is a spin lock and such xfrmdev ops may sleep, "scheduling while atomic" will be triggered when changing bond's active slave. [ 101.055189] BUG: scheduling while atomic: bash/902/0x00000200 [ 101.055726] Modules linked in: [ 101.058211] CPU: 3 PID: 902 Comm: bash Not tainted 6.9.0-rc4+ #1 [ 101.058760] Hardware name: [ 101.059434] Call Trace: [ 101.059436] [ 101.060873] dump_stack_lvl+0x51/0x60 [ 101.061275] __schedule_bug+0x4e/0x60 [ 101.061682] __schedule+0x612/0x7c0 [ 101.062078] ? __mod_timer+0x25c/0x370 [ 101.062486] schedule+0x25/0xd0 [ 101.062845] schedule_timeout+0x77/0xf0 [ 101.063265] ? asm_common_interrupt+0x22/0x40 [ 101.063724] ? __bpf_trace_itimer_state+0x10/0x10 [ 101.064215] __wait_for_common+0x87/0x190 [ 101.064648] ? usleep_range_state+0x90/0x90 [ 101.065091] cmd_exec+0x437/0xb20 [mlx5_core] [ 101.065569] mlx5_cmd_do+0x1e/0x40 [mlx5_core] [ 101.066051] mlx5_cmd_exec+0x18/0x30 [mlx5_core] [ 101.066552] mlx5_crypto_create_dek_key+0xea/0x120 [mlx5_core] [ 101.067163] ? bonding_sysfs_store_option+0x4d/0x80 [bonding] [ 101.067738] ? kmalloc_trace+0x4d/0x350 [ 101.068156] mlx5_ipsec_create_sa_ctx+0x33/0x100 [mlx5_core] [ 101.068747] mlx5e_xfrm_add_state+0x47b/0xaa0 [mlx5_core] [ 101.069312] bond_change_active_slave+0x392/0x900 [bonding] [ 101.069868] bond_option_active_slave_set+0x1c2/0x240 [bonding] [ 101.070454] __bond_opt_set+0xa6/0x430 [bonding] [ 101.070935] __bond_opt_set_notify+0x2f/0x90 [bonding] [ 101.071453] bond_opt_tryset_rtnl+0x72/0xb0 [bonding] [ 101.071965] bonding_sysfs_store_option+0x4d/0x80 [bonding] [ 101.072567] kernfs_fop_write_iter+0x10c/0x1a0 [ 101.073033] vfs_write+0x2d8/0x400 [ 101.073416] ? alloc_fd+0x48/0x180 [ 101.073798] ksys_write+0x5f/0xe0 [ 101.074175] do_syscall_64+0x52/0x110 [ 101.074576] entry_SYSCALL_64_after_hwframe+0x4b/0x53 As bond_ipsec_add_sa_all and bond_ipsec_del_sa_all are only called from bond_change_active_slave, which requires holding the RTNL lock. And bond_ipsec_add_sa and bond_ipsec_del_sa are xfrm state xdo_dev_state_add and xdo_dev_state_delete APIs, which are in user context. So ipsec_lock doesn't have to be spin lock, change it to mutex, and thus the above issue can be resolved. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | dtb-aarch64 opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-64kb opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-64kb sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-azure opensuse-leap 15.6 | 6.4.0-150600.8.17.2 | [SUSE-SU-2024:3984-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3984-1.md) | Nov 13, 2024 | | Linux | kernel-azure sles 15.6 | 6.4.0-150600.8.17.2 | [SUSE-SU-2024:3984-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3984-1.md) | Nov 13, 2024 | | Linux | kernel-coco sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-coco_debug sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-debug opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default-base opensuse-leap 15.6 | 6.4.0-150600.23.30.1.150600.12.12.6 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-default-base sles 15.6 | 6.4.0-150600.23.30.1.150600.12.12.6 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-docs opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-docs sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-kvmsmall opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-livepatch-SLE15-SP6-RT_Update_5 sles 15.6 | 1-150600.1.3.1 | [SUSE-SU-2024:3986-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3986-1.md) | Nov 13, 2024 | | Linux | kernel-livepatch-SLE15-SP6_Update_6 sles 15.6 | 1-150600.13.3.5 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-obs-build opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-obs-build sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-obs-qa opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-rt opensuse-leap 15.6 | 6.4.0-150600.10.17.1 | [SUSE-SU-2024:3986-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3986-1.md) | Nov 13, 2024 | | Linux | kernel-rt_debug opensuse-leap 15.6 | 6.4.0-150600.10.17.1 | [SUSE-SU-2024:3986-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3986-1.md) | Nov 13, 2024 | | Linux | kernel-source opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-source sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-source-azure opensuse-leap 15.6 | 6.4.0-150600.8.17.1 | [SUSE-SU-2024:3984-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3984-1.md) | Nov 13, 2024 | | Linux | kernel-source-azure sles 15.6 | 6.4.0-150600.8.17.1 | [SUSE-SU-2024:3984-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3984-1.md) | Nov 13, 2024 | | Linux | kernel-source-coco sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-source-rt opensuse-leap 15.6 | 6.4.0-150600.10.17.1 | [SUSE-SU-2024:3986-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3986-1.md) | Nov 13, 2024 | | Linux | kernel-syms opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-syms sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-syms-azure opensuse-leap 15.6 | 6.4.0-150600.8.17.1 | [SUSE-SU-2024:3984-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3984-1.md) | Nov 13, 2024 | | Linux | kernel-syms-azure sles 15.6 | 6.4.0-150600.8.17.1 | [SUSE-SU-2024:3984-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3984-1.md) | Nov 13, 2024 | | Linux | kernel-syms-coco sles 15.6 | 6.4.0-15061.9.coco15sp6.1 | [SUSE-SU-2024:4387-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4387-1.md) | Dec 19, 2024 | | Linux | kernel-syms-rt opensuse-leap 15.6 | 6.4.0-150600.10.17.1 | [SUSE-SU-2024:3986-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-3986-1.md) | Nov 13, 2024 | | Linux | kernel-zfcpdump opensuse-leap 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | kernel-zfcpdump sles 15.6 | 6.4.0-150600.23.30.1 | [SUSE-SU-2024:4318-1](https://patchblox.com/security/data/fix/linux/suse-su-2024-4318-1.md) | Dec 13, 2024 | | Linux | linux Debian 13.5 (trixie) | 6.10.9-1 | [DEBIAN-CVE-2024-46678](https://patchblox.com/security/data/fix/linux/debian-cve-2024-46678.md) | Sep 13, 2024 | | Linux | linux Debian 14 | 6.10.9-1 | [DEBIAN-CVE-2024-46678](https://patchblox.com/security/data/fix/linux/debian-cve-2024-46678.md) | Sep 13, 2024 | --- Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.