CVE-2025-38551
MediumIn 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().
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness type
CWE-667CVE-2025-38551 is a Improper Locking vulnerability
What is Improper Locking?
The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE
Affected versions
Linux kernel versions
6.11.2,
6.12
and later are affected. Fixed in
6.12.40,
6.15.8,
6.16
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2025-38551?
CVE-2025-38551 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 6.11.2 onward and has been patched in 6.12.40, 6.15.8 and 6.16. CVE-2025-38551 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-38551?
CVE-2025-38551 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2025-38551?
Yes. CVE-2025-38551 has been patched. Fixed versions include 6.12.40, 6.15.8 and 6.16. If you are running Linux kernel 6.11.2 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-38551 actively exploited?
No. CVE-2025-38551 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.