UBUNTU-CVE-2025-40352: Low severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are most likely to encounter this issue?

The reported warning occurs when a BlueField-3 SoC boots and the mlxbf_pmc platform driver is probed. Ubuntu kernel packages listed as affected include linux-bluefield as well as the specified riscv, realtime, hwe-edge, Azure, GCP, Azure FDE, and AWS 5.0 variants.

Q: Does this require an external attacker or a particular runtime action to trigger?

The available information describes a kernel lock-debug warning during device and sysfs initialization, rather than an externally triggered attack path. It is observed with CONFIG_LOCK_STAT enabled when the mlxbf_pmc driver initializes its count_clock data structure.

Q: How can an administrator recognize that the system is affected?

Affected systems may log a lockdep warning stating that a key has not been registered, with a call trace involving lockdep_init_map_type, sysfs creation functions, and mlxbf_pmc_probe. The warning is specifically associated with CONFIG_LOCK_STAT during BlueField-3 boot.

Q: What change resolves the warning?

The mlxbf_pmc driver must call sysfs_attr_init() while initializing the count_clock data structure. This registers the sysfs attribute appropriately for the kernel lock-related debug logic.

Published Dec 16, 2025

Updated

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

115 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-bluefield*

ubuntu/linux-aws-6.14*

ubuntu/linux-aws-6.17<6.17.0-1007.7~24.04.1

6.17.0-1007.7~24.04.1

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.14*

ubuntu/linux-azure-fde-6.14*

ubuntu/linux-azure-nvidia-6.14*

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gcp-6.17<6.17.0-1008.8~24.04.1

6.17.0-1008.8~24.04.1

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17<6.17.0-1008.8

6.17.0-1008.8

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17<6.17.0-1011.11

6.17.0-1011.11

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17<6.17.0-1007.7~24.04.1

6.17.0-1007.7~24.04.1

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-bluefield*

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17<6.17.0-1006.7~24.04.1

6.17.0-1006.7~24.04.1

ubuntu/linux<6.17.0-14.14

6.17.0-14.14

ubuntu/linux-aws<6.17.0-1007.7

6.17.0-1007.7

ubuntu/linux-azure<6.17.0-1008.8

6.17.0-1008.8

ubuntu/linux-azure-fde*

ubuntu/linux-gcp<6.17.0-1007.7

6.17.0-1007.7

ubuntu/linux-oracle<6.17.0-1007.7

6.17.0-1007.7

ubuntu/linux-raspi<6.17.0-1008.8

6.17.0-1008.8

ubuntu/linux-realtime<6.17.0-1006.7

6.17.0-1006.7

ubuntu/linux-riscv<6.17.0-14.14.1

6.17.0-14.14.1

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7~24.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8~24.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8
Upgrade
Upgrade ubuntu/linux-oem-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1011.11
Upgrade
Upgrade ubuntu/linux-oracle-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7~24.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1006.7~24.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.17.0-14.14
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.17.0-1007.7
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.8
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.17.0-1006.7
Upgrade
Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.
Fixed in 6.17.0-14.14.1
Compensating control
Modify the Linux platform/mellanox/mlxbf-pmc driver to call sysfs_attr_init() during initialization of the count_clock data structure.

Event History

Dec 16, 2025

CVE Published

via OSV·02:15 PM

Data Sourced

via OSV·02:15 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are most likely to encounter this issue?

The reported warning occurs when a BlueField-3 SoC boots and the mlxbf_pmc platform driver is probed. Ubuntu kernel packages listed as affected include linux-bluefield as well as the specified riscv, realtime, hwe-edge, Azure, GCP, Azure FDE, and AWS 5.0 variants.

Does this require an external attacker or a particular runtime action to trigger?

The available information describes a kernel lock-debug warning during device and sysfs initialization, rather than an externally triggered attack path. It is observed with CONFIG_LOCK_STAT enabled when the mlxbf_pmc driver initializes its count_clock data structure.

How can an administrator recognize that the system is affected?

Affected systems may log a lockdep warning stating that a key has not been registered, with a call trace involving lockdep_init_map_type, sysfs creation functions, and mlxbf_pmc_probe. The warning is specifically associated with CONFIG_LOCK_STAT during BlueField-3 boot.

What change resolves the warning?

The mlxbf_pmc driver must call sysfs_attr_init() while initializing the count_clock data structure. This registers the sysfs attribute appropriately for the kernel lock-related debug logic.

UBUNTU-CVE-2025-40352: Low severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are most likely to encounter this issue?

Does this require an external attacker or a particular runtime action to trigger?

How can an administrator recognize that the system is affected?

What change resolves the warning?

Company

Resources

Contact

Frequently Asked Questions

Which systems are most likely to encounter this issue?

Does this require an external attacker or a particular runtime action to trigger?

How can an administrator recognize that the system is affected?

What change resolves the warning?