CVE-2025-39908
BaseFortify
Publication date: 2025-10-01
Last updated on: 2025-12-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.15 (inc) to 6.16.8 (exc) |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | 6.17 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the handling of hardware timestamping (hwtstamp) ioctl operations. Specifically, the ndo hwtstamp callbacks were not consistently taking the per-device operations lock in the lower get/set paths, which is required for proper synchronization. This inconsistency could lead to race conditions or unexpected behavior when these ioctl calls are made. The fix ensures that the lower get/set paths take the ops lock, making them consistent with other ndo invocations and preventing potential kernel warnings or crashes.
How can this vulnerability impact me? :
This vulnerability could cause instability in the Linux kernel when hardware timestamping ioctl operations are performed, potentially leading to kernel warnings, crashes, or race conditions. This may affect network device functionality or reliability on systems using these ioctl calls, possibly resulting in degraded network performance or system instability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the kernel logs for warnings related to netdev locking issues, specifically messages like: "WARNING: CPU: ... at ./include/net/netdev_lock.h:70 __netdev_update_features" and call traces involving mlx5_hwtstamp_set or mlx5e_hwtstamp_set functions. You can use the command 'dmesg | grep netdev_lock' or 'journalctl -k | grep netdev_lock' to search for such warnings in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability has been resolved, as the issue is fixed by ensuring the ndo hwtstamp callbacks run under the per-device ops lock consistently. Until then, monitoring kernel logs for the described warnings can help identify if the vulnerability is being triggered.