CVE-2025-39908: net: dev_ioctl: take ops lock in hwtstamp lower paths
In the Linux kernel, the following vulnerability has been resolved:
net: dev_ioctl: take ops lock in hwtstamp lower paths
ndo hwtstamp callbacks are expected to run under the per-device ops
lock. Make the lower get/set paths consistent with the rest of ndo
invocations.
Kernel log:
WARNING: CPU: 13 PID: 51364 at ./include/net/netdev_lock.h:70 __netdev_update_features+0x4bd/0xe60
...
RIP: 0010:__netdev_update_features+0x4bd/0xe60
...
Call Trace:
<TASK>
netdev_update_features+0x1f/0x60
mlx5_hwtstamp_set+0x181/0x290 [mlx5_core]
mlx5e_hwtstamp_set+0x19/0x30 [mlx5_core]
dev_set_hwtstamp_phylib+0x9f/0x220
dev_set_hwtstamp_phylib+0x9f/0x220
dev_set_hwtstamp+0x13d/0x240
dev_ioctl+0x12f/0x4b0
sock_ioctl+0x171/0x370
__x64_sys_ioctl+0x3f7/0x900
? __sys_setsockopt+0x69/0xb0
do_syscall_64+0x6f/0x2e0
entry_SYSCALL_64_after_hwframe+0x4b/0x53
...
</TASK>
....
---[ end trace 0000000000000000 ]---
Note that the mlx5_hwtstamp_set and mlx5e_hwtstamp_set functions shown
in the trace come from an in progress patch converting the legacy ioctl
to ndo_hwtstamp_get/set and are not present in mainline.
Security readout for executives and security teams
Plain-English summary
A Linux kernel locking flaw affects hardware timestamp configuration paths. A local, low-privileged attacker may be able to trigger unsafe concurrent kernel operations, potentially compromising confidentiality, integrity, or availability. The supplied evidence does not establish remote reachability or real-world exploitation.
Executive priority
Treat as a high-priority kernel update for exposed multi-user systems, but not as an emergency remote compromise. Accelerate vendor verification and patching where untrusted local access exists. Evidence does not currently support active exploitation.
Technical view
Hardware timestamp get/set callbacks could execute without the required per-device operations lock. This inconsistency can produce unsafe concurrency during network-device feature updates, demonstrated by a kernel warning and mlx5-related trace. The source bundle reports CVSS 3.1 score 7.8 with local access and low privileges required.
Likely exposure
Exposure is limited to affected Linux kernel versions where hardware timestamp ioctl paths reach relevant network-device callbacks. The supplied version data lists 6.15, 6.16.8, and 6.17 but is insufficiently structured to determine precise affected ranges or backport status.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. The CVSS vector indicates local access, low privileges, low complexity, and no user interaction. The exact triggering prerequisites and practical impact are not documented in the bundle.
Researcher notes
The trace demonstrates a missing locking invariant, not a complete exploitation chain. It references mlx5 conversion code described as not present in mainline, so that trace should not be interpreted as mlx5-only exposure. Precise affected and fixed version boundaries require vendor confirmation.
Mitigation direction
Install a vendor-supported kernel containing the applicable upstream or stable fix.
Check distribution advisories for exact fixed package versions and backport status.
Prioritize shared or multi-user Linux systems where untrusted users have local access.
Apply normal access controls while patching; no source-backed configuration workaround is provided.
Validation and detection
Record each system's running kernel version, package release, and distribution.
Compare kernel packages against vendor advisories and the referenced stable commits.
Confirm the running kernel includes the locking fix or an equivalent vendor backport.
Review kernel logs for related netdev lock warnings without treating absence as proof of safety.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-39908 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.