Skip to main content
VulnerabilityPublished

CVE-2026-63837: Linux kernel · net: ena: PHC: Check return code before setting timestamp output

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 12 Nov 2026, 20:41 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to check the return code of ena_com_phc_get_timestamp() before setting the output timestamp in ena_phc_gettimex64(). Users should apply the official Linux kernel update containing this fix once available. No other mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's ena driver allows uninitialized or invalid timestamp data to be passed to userspace via the PTP ioctl interface. This occurs because the function ena_phc_gettimex64() sets the output timestamp without verifying the success of ena_com_phc_get_timestamp(), potentially leaking kernel stack memory or invalid hardware values. The issue has been resolved by adding a check on the return code before setting the timestamp output.

References

Community reviews

Loading reviews…