In the Linux kernel, the following vulnerability has been resolved: gve: Implement gettimex64 with -EOPNOTSUPP gve implemented a ptp_clock for sole use of do_aux_work…

Code

The project this record applies to. Exploit listings stay in References.

• Repository · git.kernel.org
• Repository · git.kernel.org

Timeline

Detection, updates, and resolution for this record.

1. Dec 8, 2025 · NIST NVD

   Detected

   In the Linux kernel, the following vulnerability has been resolved: gve: Implement gettimex64 with -EOPNOTSUPP gve implemented a ptp_clock for sole use of do_aux_work at this time. ptp_clock_gettime() and ptp_sys_offset() assume every ptp_clock has implemented either gettimex64 or gettime64. Stub gettimex64 and return -EOPNOTSUPP to prevent NULL dereferencing.

2. Oct 14, 2026 · NIST NVD

   Updated

   In the Linux kernel, the following vulnerability has been resolved: gve: Implement gettimex64 with -EOPNOTSUPP gve implemented a ptp_clock for sole use of do_aux_work at this time. ptp_clock_gettime() and ptp_sys_offset() assume every ptp_clock has implemented either gettimex64 or gettime64. Stub gettimex64 and return -EOPNOTSUPP to prevent NULL dereferencing.

Sources

• CVE.orgVulnerability recordCVE-2025-40299

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2025-40299

  30-day exploitation probability 0.2%

  first.org
• NIST NVDVulnerability recordCVE-2025-40299

  In the Linux kernel, the following vulnerability has been resolved: gve: Implement gettimex64 with -EOPNOTSUPP gve implemented a ptp_clock for sole use of do_aux_work at this time. ptp_clock_gettime() and ptp_sys_offset() assume every ptp_clock has implemented either gettimex64

  nvd.nist.gov

References

• Reference · git.kernel.org
• Reference · git.kernel.org