CVE-2025-40352: platform/mellanox: mlxbf-pmc: add sysfs_attr_init() to count_clock init
In the Linux kernel, the following vulnerability has been resolved:
platform/mellanox: mlxbf-pmc: add sysfsattrinit() to countclock init
The lock-related debug logic (CONFIGLOCKSTAT) in the kernel is noting the following warning when the BlueField-3 SOC is booted:
BUG: key ffff00008a3402a8 has not been registered! ------------[ cut here ]------------ DEBUGLOCKSWARNON(1) WARNING: CPU: 4 PID: 592 at kernel/locking/lockdep.c:4801 lockdepinitmaptype+0x1d4/0x2a0 <snip> Call trace: lockdepinitmaptype+0x1d4/0x2a0 kernfscreatefile+0x84/0x140 sysfsaddfilemodens+0xcc/0x1cc internalcreategroup+0x110/0x3d4 internalcreategroups.part.0+0x54/0xcc sysfscreategroups+0x24/0x40 deviceadd+0x6e8/0x93c deviceregister+0x28/0x40 hwmondeviceregister+0x4b0/0x8a0 devmhwmondeviceregisterwithgroups+0x7c/0xe0 mlxbfpmcprobe+0x1e8/0x3e0 [mlxbfpmc] platformprobe+0x70/0x110
The mlxbfpmc driver must call sysfsattrinit() during the initialization of the "countclock" data structure to avoid this warning.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1007.7~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1008.8~24.04.1 - Upgrade
Upgrade
ubuntu/linux-nvidia-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1008.8 - Upgrade
Upgrade
ubuntu/linux-oem-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1011.11 - Upgrade
Upgrade
ubuntu/linux-oracle-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1007.7~24.04.1 - Upgrade
Upgrade
ubuntu/linux-realtime-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1006.7~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 6.17.0-14.14 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 6.17.0-1007.7 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 6.17.0-1008.8 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 6.17.0-1007.7 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 6.17.0-1007.7 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 6.17.0-1008.8 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 6.17.0-1006.7 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 6.17.0-14.14.1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-40352?
CVE-2025-40352 is categorized as a low severity vulnerability in the Linux kernel.
How do I fix CVE-2025-40352?
You can address CVE-2025-40352 by updating to the latest stable version of the Linux kernel that includes the fix.
What systems are affected by CVE-2025-40352?
CVE-2025-40352 affects Linux kernel systems, specifically those using the BlueField-3 SOC.
What are the potential impacts of CVE-2025-40352?
The potential impacts of CVE-2025-40352 include system instability and warnings during the boot process.
When was CVE-2025-40352 disclosed?
CVE-2025-40352 was resolved as part of ongoing updates in the Linux kernel but specific disclosure dates may vary.