FKIE_CVE-2025-68779

Vulnerability from fkie_nvd - Published: 2026-01-13 16:15 - Updated: 2026-04-15 00:35
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid unregistering PSP twice PSP is unregistered twice in: _mlx5e_remove -> mlx5e_psp_unregister mlx5e_nic_cleanup -> mlx5e_psp_unregister This leads to a refcount underflow in some conditions: ------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 2 PID: 1694 at lib/refcount.c:28 refcount_warn_saturate+0xd8/0xe0 [...] mlx5e_psp_unregister+0x26/0x50 [mlx5_core] mlx5e_nic_cleanup+0x26/0x90 [mlx5_core] mlx5e_remove+0xe6/0x1f0 [mlx5_core] auxiliary_bus_remove+0x18/0x30 device_release_driver_internal+0x194/0x1f0 bus_remove_device+0xc6/0x130 device_del+0x159/0x3c0 mlx5_rescan_drivers_locked+0xbc/0x2a0 [mlx5_core] [...] Do not directly remove psp from the _mlx5e_remove path, the PSP cleanup happens as part of profile cleanup.
Impacted products
Vendor Product Version

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Avoid unregistering PSP twice\n\nPSP is unregistered twice in:\n_mlx5e_remove -\u003e mlx5e_psp_unregister\nmlx5e_nic_cleanup -\u003e mlx5e_psp_unregister\n\nThis leads to a refcount underflow in some conditions:\n------------[ cut here ]------------\nrefcount_t: underflow; use-after-free.\nWARNING: CPU: 2 PID: 1694 at lib/refcount.c:28 refcount_warn_saturate+0xd8/0xe0\n[...]\n mlx5e_psp_unregister+0x26/0x50 [mlx5_core]\n mlx5e_nic_cleanup+0x26/0x90 [mlx5_core]\n mlx5e_remove+0xe6/0x1f0 [mlx5_core]\n auxiliary_bus_remove+0x18/0x30\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n mlx5_rescan_drivers_locked+0xbc/0x2a0 [mlx5_core]\n[...]\n\nDo not directly remove psp from the _mlx5e_remove path, the PSP cleanup\nhappens as part of profile cleanup."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nnet/mlx5e: Evitar desregistrar PSP dos veces\n\nPSP se desregistra dos veces en:\n_mlx5e_remove -\u0026gt; mlx5e_psp_unregister\nmlx5e_nic_cleanup -\u0026gt; mlx5e_psp_unregister\n\nEsto conduce a un refcount underflow en algunas condiciones:\n------------[ corte aqu\u00ed ]------------\nrefcount_t: underflow; uso despu\u00e9s de liberaci\u00f3n.\nADVERTENCIA: CPU: 2 PID: 1694 en lib/refcount.c:28 refcount_warn_saturate+0xd8/0xe0\n[...]\n mlx5e_psp_unregister+0x26/0x50 [mlx5_core]\n mlx5e_nic_cleanup+0x26/0x90 [mlx5_core]\n mlx5e_remove+0xe6/0x1f0 [mlx5_core]\n auxiliary_bus_remove+0x18/0x30\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n mlx5_rescan_drivers_locked+0xbc/0x2a0 [mlx5_core]\n[...]\n\nNo eliminar directamente psp de la ruta _mlx5e_remove, la limpieza de PSP ocurre como parte de la limpieza del perfil."
    }
  ],
  "id": "CVE-2025-68779",
  "lastModified": "2026-04-15T00:35:42.020",
  "metrics": {},
  "published": "2026-01-13T16:15:57.550",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/35e93736f69963337912594eb3951ab320b77521"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/e12c912f92ccea671b514caf371f28485714bb4b"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Deferred"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…