FKIE_CVE-2025-40352

Vulnerability from fkie_nvd - Published: 2025-12-16 14:15 - Updated: 2026-10-14 13:10
Severity
Summary
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.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/46be1f5aae82b4136f676528ff091629697c7719
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a7b4747d8e0e7871c3d4971cded1dcc9af6af9e9
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/platform/mellanox/mlxbf-pmc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "46be1f5aae82b4136f676528ff091629697c7719",
              "status": "affected",
              "version": "5efc800975d9a66cf7e7684c07d4c1928f025972",
              "versionType": "git"
            },
            {
              "lessThan": "a7b4747d8e0e7871c3d4971cded1dcc9af6af9e9",
              "status": "affected",
              "version": "5efc800975d9a66cf7e7684c07d4c1928f025972",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/platform/mellanox/mlxbf-pmc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.17.*",
              "status": "unaffected",
              "version": "6.17.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.18",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/mellanox: mlxbf-pmc: add sysfs_attr_init() to count_clock init\n\nThe lock-related debug logic (CONFIG_LOCK_STAT) in the kernel is noting\nthe following warning when the BlueField-3 SOC is booted:\n\n  BUG: key ffff00008a3402a8 has not been registered!\n  ------------[ cut here ]------------\n  DEBUG_LOCKS_WARN_ON(1)\n  WARNING: CPU: 4 PID: 592 at kernel/locking/lockdep.c:4801 lockdep_init_map_type+0x1d4/0x2a0\n\u003csnip\u003e\n  Call trace:\n   lockdep_init_map_type+0x1d4/0x2a0\n   __kernfs_create_file+0x84/0x140\n   sysfs_add_file_mode_ns+0xcc/0x1cc\n   internal_create_group+0x110/0x3d4\n   internal_create_groups.part.0+0x54/0xcc\n   sysfs_create_groups+0x24/0x40\n   device_add+0x6e8/0x93c\n   device_register+0x28/0x40\n   __hwmon_device_register+0x4b0/0x8a0\n   devm_hwmon_device_register_with_groups+0x7c/0xe0\n   mlxbf_pmc_probe+0x1e8/0x3e0 [mlxbf_pmc]\n   platform_probe+0x70/0x110\n\nThe mlxbf_pmc driver must call sysfs_attr_init() during the\ninitialization of the \"count_clock\" data structure to avoid\nthis warning."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nplatform/mellanox: mlxbf-pmc: a\u00f1adir sysfs_attr_init() a la inicializaci\u00f3n de count_clock\n\nLa l\u00f3gica de depuraci\u00f3n relacionada con bloqueos (CONFIG_LOCK_STAT) en el kernel est\u00e1 registrando la siguiente advertencia cuando se arranca el SOC BlueField-3:\n\n  BUG: \u00a1la clave ffff00008a3402a8 no ha sido registrada!\n  ------------[ cortar aqu\u00ed ]------------\n  DEBUG_LOCKS_WARN_ON(1)\n  WARNING: CPU: 4 PID: 592 en kernel/locking/lockdep.c:4801 lockdep_init_map_type+0x1d4/0x2a0\n\u003crecorte\u003e\n  Traza de llamada:\n   lockdep_init_map_type+0x1d4/0x2a0\n   __kernfs_create_file+0x84/0x140\n   sysfs_add_file_mode_ns+0xcc/0x1cc\n   internal_create_group+0x110/0x3d4\n   internal_create_groups.part.0+0x54/0xcc\n   sysfs_create_groups+0x24/0x40\n   device_add+0x6e8/0x93c\n   device_register+0x28/0x40\n   __hwmon_device_register+0x4b0/0x8a0\n   devm_hwmon_device_register_with_groups+0x7c/0xe0\n   mlxbf_pmc_probe+0x1e8/0x3e0 [mlxbf_pmc]\n   platform_probe+0x70/0x110\n\nEl controlador mlxbf_pmc debe llamar a sysfs_attr_init() durante la inicializaci\u00f3n de la estructura de datos \u0027count_clock\u0027 para evitar esta advertencia."
    }
  ],
  "id": "CVE-2025-40352",
  "lastModified": "2026-10-14T13:10:00.187",
  "metrics": {},
  "published": "2025-12-16T14:15:47.083",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/46be1f5aae82b4136f676528ff091629697c7719"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/a7b4747d8e0e7871c3d4971cded1dcc9af6af9e9"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Deferred"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.