Improper Locking The advisory has been revoked - it doesn't affect any version of package kernel-headers (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-RHEL10-KERNELHEADERS-11957636
- published18 Aug 2025
- disclosed16 Aug 2025
Introduced: 16 Aug 2025
CVE-2025-38551 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:10.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-headers package and not the kernel-headers package as distributed by RHEL.
In the Linux kernel, the following vulnerability has been resolved:
virtio-net: fix recursived rtnl_lock() during probe()
The deadlock appears in a stack trace like:
virtnet_probe() rtnl_lock() virtio_config_changed_work() netdev_notify_peers() rtnl_lock()
It happens if the VMM sends a VIRTIO_NET_S_ANNOUNCE request while the virtio-net driver is still probing.
The config_work in probe() will get scheduled until virtnet_open() enables the config change notification via virtio_config_driver_enable().
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2388923
- https://access.redhat.com/security/cve/CVE-2025-38551
- https://git.kernel.org/stable/c/3859f137b3c1fa1f0031d54263234566bdcdd7aa
- https://git.kernel.org/stable/c/4e7c46362550b229354aeb52038f414e231b0037
- https://git.kernel.org/stable/c/be5dcaed694e4255dc02dd0acfe036708c535def