# CVE-2025-40352: platform/mellanox: mlxbf-pmc: add sysfs_attr_init() to count_clock init

> Missing sysfs attribute initialization in the Mellanox BlueField-3 PMC driver triggers a kernel warning and potential instability during boot.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40352, DEBIAN-CVE-2025-40352, GHSA-5r3f-3vjw-2jp6, UBUNTU-CVE-2025-40352

## What is CVE-2025-40352?

CVE-2025-40352 is a vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

platform/mellanox: mlxbf-pmc: add sysfs_attr_init() to count_clock init

The lock-related debug logic (CONFIG_LOCK_STAT) in the kernel is noting
the following warning when the BlueField-3 SOC is booted:

  BUG: key ffff00008a3402a8 has not been registered!
  ------------[ cut here ]------------
  DEBUG_LOCKS_WARN_ON(1)
  WARNING: CPU: 4 PID: 592 at kernel/locking/lockdep.c:4801 lockdep_init_map_type+0x1d4/0x2a0
<snip>
  Call trace:
   lockdep_init_map_type+0x1d4/0x2a0
   __kernfs_create_file+0x84/0x140
   sysfs_add_file_mode_ns+0xcc/0x1cc
   internal_create_group+0x110/0x3d4
   internal_create_groups.part.0+0x54/0xcc
   sysfs_create_groups+0x24/0x40
   device_add+0x6e8/0x93c
   device_register+0x28/0x40
   __hwmon_device_register+0x4b0/0x8a0
   devm_hwmon_device_register_with_groups+0x7c/0xe0
   mlxbf_pmc_probe+0x1e8/0x3e0 [mlxbf_pmc]
   platform_probe+0x70/0x110

The mlxbf_pmc driver must call sysfs_attr_init() during the
initialization of the "count_clock" data structure to avoid
this warning.

## Which versions are affected by CVE-2025-40352?


## How do I fix CVE-2025-40352?

Apply the vendor's patch.

## Is CVE-2025-40352 being exploited?

There is no known exploitation of CVE-2025-40352 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40352 and fix it if it is affected.

What it is: CVE-2025-40352 is a vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40352 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40352/ (Markdown: https://insights.sbomify.com/CVE-2025-40352/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40352
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40352
- OSV: https://osv.dev/vulnerability/CVE-2025-40352

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40352/
Summaries are generated and may contain mistakes; the official description above is the record.