CVE-2026-64251
CVE-2026-64251
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.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| linux_kernel linux |
≥ 6.11; < 6.12.95 (affected, custom) | NVD |
| linux_kernel linux |
≥ 6.13; < 6.18.38 (affected, custom) | NVD |
| linux_kernel linux |
≥ 6.19; < 7.1.3 (affected, custom) | NVD |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
NVD applicability configurations (1)
These expressions retain AND/OR operators, negation, and required environmental products. A listed product is not sufficient to establish exposure when additional conditions apply.
[
{
"negate": false,
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.95",
"versionStartIncluding": "6.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.38",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.3",
"versionStartIncluding": "6.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
]CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/257595adf9dac15ae1edd9d07753fbc576a7583d416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
- https://git.kernel.org/stable/c/73569a44fca2992f0ca4a4c0104069741b9873a0416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
- https://git.kernel.org/stable/c/ba0b9f04c7a5f9887b8ce672eaf049502c0548ec416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
- https://git.kernel.org/stable/c/e91df6d273445c03f5aa302bfe147eda33d45794416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.