CVE-2025-39832
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-16

Last updated on: 2025-12-03

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix lockdep assertion on sync reset unload event Fix lockdep assertion triggered during sync reset unload event. When the sync reset flow is initiated using the devlink reload fw_activate option, the PF already holds the devlink lock while handling unload event. In this case, delegate sync reset unload event handling back to the devlink callback process to avoid double-locking and resolve the lockdep warning. Kernel log: WARNING: CPU: 9 PID: 1578 at devl_assert_locked+0x31/0x40 [...] Call Trace: <TASK> mlx5_unload_one_devl_locked+0x2c/0xc0 [mlx5_core] mlx5_sync_reset_unload_event+0xaf/0x2f0 [mlx5_core] process_one_work+0x222/0x640 worker_thread+0x199/0x350 kthread+0x10b/0x230 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x8e/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK>
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-16
Last Modified
2025-12-03
Generated
2026-06-16
AI Q&A
2025-09-16
EPSS Evaluated
2026-06-15
NVD
CVE-2025-39832
Affected Vendors & Products
Showing 6 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.5 (inc) to 6.6.104 (exc)
linux linux_kernel From 6.7 (inc) to 6.12.45 (exc)
linux linux_kernel From 6.13 (inc) to 6.16.5 (exc)
linux linux_kernel 6.17
linux linux_kernel 6.17
linux linux_kernel 6.17
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-667 The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a lockdep assertion issue in the Linux kernel's mlx5 driver. It occurs during a synchronous reset unload event when the devlink lock is held twice, causing a double-locking problem. The fix delegates the unload event handling back to the devlink callback process to avoid this double-locking and resolve the lockdep warning.

Impact Analysis

This vulnerability can cause kernel warnings and potentially lead to system instability or crashes due to improper lock handling during device reset events in the mlx5 driver. It affects the reliability of the system when performing synchronous reset unload operations.

Detection Guidance

This vulnerability can be detected by monitoring the kernel logs for the specific lockdep assertion warning related to the mlx5 driver. Look for messages similar to: "WARNING: CPU: <cpu> PID: <pid> at devl_assert_locked+0x31/0x40" followed by a call trace involving mlx5_unload_one_devl_locked and mlx5_sync_reset_unload_event. You can use the command 'dmesg | grep devl_assert_locked' or 'journalctl -k | grep devl_assert_locked' to find these warnings in the kernel logs.

Mitigation Strategies

To mitigate this vulnerability, update the Linux kernel to a version where the fix for the lockdep assertion on sync reset unload event in the mlx5 driver has been applied. Until the update is applied, avoid triggering the sync reset flow using the devlink reload fw_activate option on affected systems to prevent the double-locking issue.

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