Answer in brief
CVE-2026-64251 records a Unknown severity vulnerability in pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <ba0b9f04c7a5f9887b8ce672eaf049502c0548ec || >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <e91df6d273445c03f5aa302bfe147eda33d45794 || >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <73569a44fca2992f0ca4a4c0104069741b9873a0 || >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <257595adf9dac15ae1edd9d07753fbc576a7583d | ba0b9f04c7a5f9887b8ce672eaf049502c0548ec, e91df6d273445c03f5aa302bfe147eda33d45794, 73569a44fca2992f0ca4a4c0104069741b9873a0, 257595adf9dac15ae1edd9d07753fbc576a7583d |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64251 records a Unknown severity vulnerability in pwrseq: core: fix use-after-free in pwrseq_debugfs_seq_next(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <ba0b9f04c7a5f9887b8ce672eaf049502c0548ec || >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <e91df6d273445c03f5aa302bfe147eda33d45794 || >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <73569a44fca2992f0ca4a4c0104069741b9873a0 || >=249ebf3f65f8530beb2cbfb91bff1d83ba88d23c <257595adf9dac15ae1edd9d07753fbc576a7583d | ba0b9f04c7a5f9887b8ce672eaf049502c0548ec, e91df6d273445c03f5aa302bfe147eda33d45794, 73569a44fca2992f0ca4a4c0104069741b9873a0, 257595adf9dac15ae1edd9d07753fbc576a7583d |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jul 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.