CVE-2025-39733
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-07

Last updated on: 2025-11-25

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-07
Last Modified
2025-11-25
Generated
2026-06-16
AI Q&A
2025-09-07
EPSS Evaluated
2026-06-14
NVD
CVE-2025-39733
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
linux linux_kernel 6.15
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves issues with locking mechanisms related to team devices. Specifically, there were ordering issues with lower instance locks and the team lock. The fix involved replacing the team lock with the rtnl lock to protect the team device, similar to how bonding devices are handled. This change improves the locking order and prevents potential concurrency problems.

Impact Analysis

The vulnerability could lead to concurrency issues or race conditions in the Linux kernel's handling of team devices, potentially causing system instability or unexpected behavior in network device management.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-39733. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart