NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 257595adf9dac15ae1edd9d07753fbc576a7583d, 73569a44fca2992f0ca4a4c0104069741b9873a0, ba0b9f04c7a5f9887b8ce672eaf049502c0548ec.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 257595adf9dac15ae1edd9d07753fbc576a7583d, 73569a44fca2992f0ca4a4c0104069741b9873a0, ba0b9f04c7a5f9887b8ce672eaf049502c0548ec or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 return was non-NULL). - stop(): put_device(data) to release the last iterated device's reference, with a NULL guard since stop() may be called with NULL when start() returned NULL or next() reached end-of-sequence.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

openSUSE-SU-2026:11476-1

Published: Jul 24, 2026
Updated: Nov 8, 2026
EPSS: 0.1% · 6th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: —
CNA · Linux: 7.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel6.11 and later · before 6.12.95
linux linux kernel6.13 and later · before 6.18.38
linux linux kernel6.19 and later · before 7.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 6.11affected
- 249ebf3f65f8530beb2cbfb91bff1d83ba88d23c and later · before ba0b9f04c7a5f9887b8ce672eaf049502c0548ecaffected · git
- 249ebf3f65f8530beb2cbfb91bff1d83ba88d23c and later · before e91df6d273445c03f5aa302bfe147eda33d45794affected · git
- 249ebf3f65f8530beb2cbfb91bff1d83ba88d23c and later · before 73569a44fca2992f0ca4a4c0104069741b9873a0affected · git
- 249ebf3f65f8530beb2cbfb91bff1d83ba88d23c and later · before 257595adf9dac15ae1edd9d07753fbc576a7583daffected · git
- before 6.11not affected · semver
- 6.12.95 and later · up to and including 6.12.*not affected · semver
- 6.18.38 and later · up to and including 6.18.*not affected · semver
- 7.1.3 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:13	linux	before 6.12.95-1	6.12.95-1
Debian:14	linux	before 7.1.3-1	7.1.3-1
openSUSE:Tumbleweed	kernel-source	before 7.1.7-1.1	7.1.7-1.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-64249Jul 24, 2026 · fpga: region: fix use-after-free in child_regions_with_firmware()
31Monitor
← EarlierCVE-2026-64250Jul 24, 2026 · LoongArch: Report dying CPU to RCU in stop_this_cpu()
22Monitor
Later →CVE-2026-64253Jul 24, 2026 · kernel/fork: clear PF_BLOCK_TS in copy_process()
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	257595adf9dac15ae1edd9d07753fbc576a7583d	Vendor (CNA)
Linux Linux	73569a44fca2992f0ca4a4c0104069741b9873a0	Vendor (CNA)
Linux Linux	ba0b9f04c7a5f9887b8ce672eaf049502c0548ec	Vendor (CNA)
Linux Linux	e91df6d273445c03f5aa302bfe147eda33d45794	Vendor (CNA)
debian:linux	6.12.95-1 · Debian:13	Package registry (OSV)
opensuse:kernel-source	7.1.7-1.1 · openSUSE:Tumbleweed	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0636 · Jul 27, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/257595adf9dac15ae1edd9d07753fbc576a7583d

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records