Menu

Star on GitHub · 3.2k

CVE-2025-68217

In the Linux kernel, the following vulnerability has been resolved: Input: pegasus-notetaker - fix potential out-of-bounds access In the pegasus_notetaker driver, the pegasus_probe() function all…

Published Dec 16, 2025EPSS 0.22%

Overview

CVE-2025-68217 is a known-severity vulnerability. It was published on December 16, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

Input: pegasus-notetaker - fix potential out-of-bounds access

In the pegasus_notetaker driver, the pegasus_probe() function allocates

the URB transfer buffer using the wMaxPacketSize value from

the endpoint descriptor. An attacker can use a malicious USB descriptor

to force the allocation of a very small buffer.

Subsequently, if the device sends an interrupt packet with a specific

pattern (e.g., where the first byte is 0x80 or 0x42),

the pegasus_parse_packet() function parses the packet without checking

the allocated buffer size. This leads to an out-of-bounds memory access.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-68217?

CVE-2025-68217 is a known-severity vulnerability. It was published on December 16, 2025.

How severe is CVE-2025-68217?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-68217?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-68217?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68217 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.