Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0

Not known to be exploited.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel by verifying the return code before setting the timestamp output. Users should apply the official Linux kernel updates that include this fix. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; users should consult the Linux kernel vendor advisory or distribution security updates for the exact fixed versions.

Description

A vulnerability in the Linux kernel's ena driver related to the PHC timestamp output was resolved. The function ena_phc_gettimex64() improperly sets the output timestamp parameter without verifying the success of ena_com_phc_get_timestamp(). This can lead to leaking uninitialized stack memory or invalid hardware values to userspace, causing an information leak and correctness issues. The fix involves checking the return code before setting the output timestamp.

References

Community reviews

Loading reviews…