regmap: slimbus: fix bus_context pointer in regmap init calls
CVE-2025-40317 is fixed in 42 products on 1 platform, first by DEBIAN-CVE-2025-40317, released December 8, 2025. It is not reported as exploited. Patch Radar priority: High.
In the Linux kernel, the following vulnerability has been resolved: regmap: slimbus: fix bus_context pointer in regmap init calls Commit 4e65bda8273c ("ASoC: wcd934x: fix error handling in wcd934x_codec_parse_data()") revealed the problem in the slimbus regmap. That commit breaks audio playback, for instance, on sdm845 Thundercomm Dragonboard 845c board: Unable to handle kernel paging request at virtual address ffff8000847cbad4 ... CPU: 5 UID: 0 PID: 776 Comm: aplay Not tainted 6.18.0-rc1-00028-g7ea30958b305 #11 PREEMPT Hardware name: Thundercomm Dragonboard 845c (DT) ... Call trace: slim_xfer_msg+0x24/0x1ac [slimbus] (P) slim_read+0x48/0x74 [slimbus] regmap_slimbus_read+0x18/0x24 [regmap_slimbus] _regmap_raw_read+0xe8/0x174 _regmap_bus_read+0x44/0x80 _regmap_read+0x60/0xd8 _regmap_update_bits+0xf4/0x140 _regmap_select_page+0xa8/0x124 _regmap_raw_write_impl+0x3b8/0x65c _regmap_bus_raw_write+0x60/0x80 _regmap_write+0x58/0xc0 regmap_write+0x4c/0x80 wcd934x_hw_params+0x494/0x8b8 [snd_soc_wcd934x] snd_soc_dai_hw_params+0x3c/0x7c [snd_soc_core] __soc_pcm_hw_params+0x22c/0x634 [snd_soc_core] dpcm_be_dai_hw_params+0x1d4/0x38c [snd_soc_core] dpcm_fe_dai_hw_params+0x9c/0x17c [snd_soc_core] snd_pcm_hw_params+0x124/0x464 [snd_pcm] snd_pcm_common_ioctl+0x110c/0x1820 [snd_pcm] snd_pcm_ioctl+0x34/0x4c [snd_pcm] __arm64_sys_ioctl+0xac/0x104 invoke_syscall+0x48/0x104 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x34/0xec el0t_64_sync_handler+0xa0/0xf0 el0t_64_sync+0x198/0x19c The __devm_regmap_init_slimbus() started to be used instead of __regmap_init_slimbus() after the commit mentioned above and turns out the incorrect bus_context pointer (3rd argument) was used in __devm_regmap_init_slimbus(). It should be just "slimbus" (which is equal to &slimbus->dev). Correct it. The wcd934x codec seems to be the only or the first user of devm_regmap_init_slimbus() but we should fix it till the point where __devm_regmap_init_slimbus() was introduced therefore two "Fixes" tags. While at this, also correct the same argument in __regmap_init_slimbus().
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool6.12 · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| bpftool6.12-debuginfo · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| dtb-aarch64 · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| dtb-aarch64 · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-64kb · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-64kb · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-64kb · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-azure · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.20.24.1 | SUSE-SU-2026:0281-1 | Jan 23, 2026 |
| kernel-azure · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-debug · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-default · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-default · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-default-base · opensuse-leap 15.6 | 6.4.0-150600.23.84.1.150600.12.38.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default-base · opensuse-leap 16.0 | 6.12.0-160000.9.1.160000.2.6 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-default-base · sles 15.6 | 6.4.0-150600.23.84.1.150600.12.38.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.28.1.150700.17.19.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-default-base · sles 16.0 | 6.12.0-160000.9.1.160000.2.6 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-docs · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-docs · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-docs · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-docs · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-kvmsmall · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-kvmsmall · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-kvmsmall · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-livepatch-6.12.58-82.121 · amzn 2023 | 1:1.0-0.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel-livepatch-SLE15-SP6_Update_19 · sles 15.6 | 1-150600.13.3.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-livepatch-SLE15-SP7-RT_Update_8 · sles 15.7 | 1-150700.1.3.1 | SUSE-SU-2026:0278-1 | Jan 23, 2026 |
| kernel-livepatch-SLE15-SP7_Update_8 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-obs-build · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-obs-build · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-obs-build · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-obs-qa · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-obs-qa · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-obs-qa · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-rt · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-source · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-source · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-source · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-source · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-source-azure · sles 15.7 | 6.4.0-150700.20.24.1 | SUSE-SU-2026:0281-1 | Jan 23, 2026 |
| kernel-syms · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-syms · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-syms · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-syms · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel-syms-azure · sles 15.7 | 6.4.0-150700.20.24.1 | SUSE-SU-2026:0281-1 | Jan 23, 2026 |
| kernel-zfcpdump · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-zfcpdump · opensuse-leap 16.0 | 6.12.0-160000.9.1 | OPENSUSE-SU-2026:20145-1 | Feb 2, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-zfcpdump · sles 16.0 | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 | Feb 2, 2026 |
| kernel6.12 · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-debuginfo · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-debuginfo-common-aarch64 · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-debuginfo-common-x86_64 · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-devel · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-headers · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-libbpf · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-libbpf-debuginfo · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-libbpf-devel · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-libbpf-static · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-modules-extra · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-modules-extra-common · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-tools · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-tools-debuginfo · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| kernel6.12-tools-devel · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| linux · Debian 12.15 (bookworm) | 6.1.159-1 | DEBIAN-CVE-2025-40317 | Dec 8, 2025 |
| linux · Debian 13.5 (trixie) | 6.12.63-1 | DEBIAN-CVE-2025-40317 | Dec 8, 2025 |
| linux · Debian 14 | 6.17.8-1 | DEBIAN-CVE-2025-40317 | Dec 8, 2025 |
| perf6.12 · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| perf6.12-debuginfo · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| python3-perf6.12 · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
| python3-perf6.12-debuginfo · amzn 2023 | 1:6.12.58-82.121.amzn2023 | ALAS2023-2026-1495 | Mar 16, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
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.