CVE-2025-71226
PTP Clock Registration Warning in Linux iwlwifi Driver
Publication date: 2026-02-18
Last updated on: 2026-02-27
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| intel | iwlwifi | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability relates to the Linux kernel's iwlwifi driver for Intel wireless devices. A recent kernel commit requires that PTP (Precision Time Protocol) clocks registered via ptp_clock_register must have the settime64 operation implemented. However, the MVM and MLD PTP clock implementations in iwlwifi do not implement this settime64 function, causing warnings and failures when the PTP clock tries to register.
To address this, instead of implementing the actual settime64 functionality (which lacks a suitable firmware interface), a stub function was created that simply returns an error code (-EOPTNOTSUPP). This suppresses the warning and allows the PTP clock to register successfully without providing full settime64 support.
How can this vulnerability impact me? :
The impact of this vulnerability is primarily related to system warnings and the inability to fully register the PTP clock for Intel wireless devices using the iwlwifi driver. Without the stub fix, users may see warnings during interface startup and the PTP clock registration may fail.
Functionally, this means that precise time synchronization features relying on the PTP clock might not work correctly or be available on affected devices. However, since the fix involves a stub that suppresses warnings and allows registration, the impact is mitigated but the full settime64 functionality remains unsupported.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing warning messages related to the PTP clock registration in the system logs when the iwlwifi interface starts up.
- Check system logs for warnings similar to: "WARNING: drivers/ptp/ptp_clock.c:325 at ptp_clock_register+0x2c8/0x6b8, CPU#1: wpa_supplicant/469"
- Look for messages like: "iwlwifi 0000:01:00.0: Failed to register PHC clock (-22)"
You can use commands such as 'dmesg | grep ptp_clock_register' or 'journalctl -k | grep iwlwifi' to find these warnings in kernel logs.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by implementing a stub for the settime64 function in the iwlwifi MVM/MLD PTP clock implementation that suppresses the warning and allows the PTP clock to be registered.
Immediate mitigation involves updating the Linux kernel to a version that includes the commit dfb073d32cac or later, which contains this fix.