Deadlock The advisory has been revoked - it doesn't affect any version of package kernel-rt-trace-devel  (opens in a new tab)


Threat Intelligence

EPSS
0.11% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS7-KERNELRTTRACEDEVEL-10609002
  • published4 Jul 2025
  • disclosed3 Jul 2025

Introduced: 3 Jul 2025

CVE-2025-38114  (opens in a new tab)
CWE-833  (opens in a new tab)

Amendment

The Centos security team deemed this advisory irrelevant for Centos:7.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-trace-devel package and not the kernel-rt-trace-devel package as distributed by Centos.

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

e1000: Move cancel_work_sync to avoid deadlock

Previously, e1000_down called cancel_work_sync for the e1000 reset task (via e1000_down_and_stop), which takes RTNL.

As reported by users and syzbot, a deadlock is possible in the following scenario:

CPU 0:

  • RTNL is held
  • e1000_close
  • e1000_down
  • cancel_work_sync (cancel / wait for e1000_reset_task())

CPU 1:

  • process_one_work
  • e1000_reset_task
  • take RTNL

To remedy this, avoid calling cancel_work_sync from e1000_down (e1000_reset_task does nothing if the device is down anyway). Instead, call cancel_work_sync for e1000_reset_task when the device is being removed.