Menu

Star on GitHub · 3.2k

CVE-2026-64251

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next() pwrseq_debugfs_seq_next() declares 'next' with __free(put_device)…

Published Jul 24, 2026CWE-416EPSS 0.12%

Overview

CVE-2026-64251 is a high-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next()

pwrseq_debugfs_seq_next() declares 'next' with __free(put_device),

which causes put_device() to be called on the returned pointer when

the variable goes out of scope. This results in a use-after-free

since the seq_file framework receives a pointer whose reference has

already been dropped.

Simply removing __free(put_device) would fix the UAF but would leak

the reference acquired by bus_find_next_device(), as stop() only

calls up_read(&pwrseq_sem) and never releases the device reference.

Fix this by making the reference counting consistent across all

seq_file callbacks, matching the standard pattern used by PCI and

SCSI:

- start(): use get_device() so it returns a referenced pointer.

- next(): explicitly put_device(curr) to release the previous

device's reference (no NULL check needed - the seq_file framework

only calls next() while the previous retu

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-2026-64251?

CVE-2026-64251 is a high-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-64251?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-64251?

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-2026-64251?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64251 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.

Related HIGH CVEs from 2026

View all