CVE-2025-21814: ptp: Ensure info->enable callback is always set
In the Linux kernel, the following vulnerability has been resolved:
ptp: Ensure info->enable callback is always set
The ioctl and sysfs handlers unconditionally call the ->enable callback.
Not all drivers implement that callback, leading to NULL dereferences.
Example of affected drivers: ptp_s390.c, ptp_vclock.c and ptp_mock.c.
Instead use a dummy callback if no better was specified by the driver.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash systems that expose certain Precision Time Protocol drivers. Kernel ioctl and sysfs paths call a driver callback that may not exist, causing a NULL pointer dereference. The public record does not provide CVSS, confirmed exploitation, or evidence of remote compromise.
Executive priority
Treat as a scheduled kernel maintenance issue unless critical systems expose affected PTP functionality. Prioritize internet-facing appliances, industrial systems, and uptime-sensitive hosts after vendor applicability is confirmed.
Technical view
The PTP subsystem unconditionally invokes info->enable from ioctl and sysfs handlers. Drivers such as ptp_s390.c, ptp_vclock.c, and ptp_mock.c may lack that callback, causing NULL dereference. Stable kernel commits add a dummy callback when no driver callback is provided.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds with relevant PTP drivers present and reachable through ioctl or sysfs interfaces. Appliance and industrial products may be affected if their vendor kernel includes the vulnerable code.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, exploit code, or remote attack evidence. The described impact is a kernel NULL dereference, which most directly suggests denial of service if reachable by a local or otherwise authorized interface user.
Researcher notes
Evidence supports a PTP NULL callback dereference fixed by assigning a dummy enable callback. Source data lacks CVSS, CWE, exploitability detail, and precise product matrices beyond Linux, Debian advisories, and Siemens advisory references.
Mitigation direction
Apply vendor kernel updates containing the listed stable Linux fixes.
Review Debian LTS advisories if using Debian-based systems.
Review Siemens advisories for listed industrial product exposure.
If no vendor update is available, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Check whether affected PTP drivers are built, loaded, or exposed.
Confirm installed kernels include the stable fix commits or vendor backports.
Review logs for PTP-related kernel oops or panic events.
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-21814 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.
0CVSS vectors
3Timeline events
2ADP providers
13Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 27, 2025, 20:04 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.