CVE-2026-63837
Last modified
CVE-2026-63837 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: net: ena: PHC: Check return code before setting timestamp output ena_phc_gettimex64() is setting the output parameter regardless of whether ena_com_phc_get_timestamp() succeeded or failed. When ena_com_phc_get_timestamp() returns an error, the timestamp parameter may contain uninitialized stack memory (e.g., when PHC is disabled or in blocked state) or invalid hardware values. Passing these to userspace via the PTP ioctl is both a security issue (information leak) and a correctness bug. Fix by checking the return code after releasing the lock and only setting the output timestamp on success.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: ena: PHC: Check return code before setting timestamp output ena_phc_gettimex64() is setting the output parameter regardless of whether ena_com_phc_get_timestamp() succeeded or failed. When ena_com_phc_get_timestamp() returns an error, the timestamp parameter may contain uninitialized stack memory (e.g., when PHC is disabled or in blocked state) or invalid hardware values. Passing these to userspace via the PTP ioctl is both a security issue (information leak) and a correctness bug. Fix by checking the return code after releasing the lock and only setting the output timestamp on success.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= e0ea34158ee8c4f7536cd781010339ff28c0d24c, < bddf59818ae5102e6d82a4dae5add6df8da38fb0; >= e0ea34158ee8c4f7536cd781010339ff28c0d24c, < edcb049d836e175e7b3d5e0d05657104545b5e65; >= e0ea34158ee8c4f7536cd781010339ff28c0d24c, < 24a08d7d6218d60c033015cf4870b6096446e734 |
| Linux | Linux | 6.17 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-63837?
How severe is CVE-2026-63837?
How do I fix CVE-2026-63837?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63831In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63832In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63833In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-63834In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63835In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63836In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63838In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63839In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6384A flaw was found in gimp. This buffer overflow vulnerability…7.8
- CVE-2026-63840In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63841In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63842In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-63837?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
