{"id":"CVE-2026-98016","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix use-after-free race in sample_restore_put()\n\nConcurrent teardown of TC sample rules sharing the same restore\ncontext may re-read restore->count after dro…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix use-after-free race in sample_restore_put()\n\nConcurrent teardown of TC sample rules sharing the same restore\ncontext may re-read restore->count after dro…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 36a3196256bf3310e5e7142b0e61787f7a201abd < 3efd1a1938cbb33c53b0d75e55b6c0fe2ebad79a","Linux >= 36a3196256bf3310e5e7142b0e61787f7a201abd < 72324da8eeca269db9196c2a555abf72eb0385c5","Linux >= 36a3196256bf3310e5e7142b0e61787f7a201abd < 1daecd76ab9e5f055fe3970462410ad1d40bd177","Linux >= 36a3196256bf3310e5e7142b0e61787f7a201abd < af3aef0245abbab5e9f6302e7a7d6407187afb71","Linux 5.13"],"published":"2026-09-25","updated":"2026-09-25","sourceUpdated":"2026-09-25T11:17:30.040","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-98016","references":[{"url":"https://git.kernel.org/stable/c/1daecd76ab9e5f055fe3970462410ad1d40bd177","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/3efd1a1938cbb33c53b0d75e55b6c0fe2ebad79a","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/72324da8eeca269db9196c2a555abf72eb0385c5","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/af3aef0245abbab5e9f6302e7a7d6407187afb71","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-25T11:06:38.857Z","slug":"CVE-2026-98016","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix use-after-free race in sample_restore_put()\n\nConcurrent teardown of TC sample rules sharing the same restore\ncontext may re-read restore->count after dropping restore_lock.\nAt that point another thread may already have completed cleanup and\nfreed the restore object.\n\nUse the result of the refcount decrement while holding restore_lock to\ndetermine whether cleanup is needed.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}