Answer in brief
CVE-2026-80671 records a Critical severity (CVSS 9.3) vulnerability in perf sched: Fix register_pid() overflow, strcpy, and BUG_ON. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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.
CVSS is 9.3. 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <652cea73b7b7b7c622a2be670e44e3c499c6d49f || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <5ea1dcc9418c4e06ce29ed5170596f497ba86872 || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <5949d339f5ec98752d56dcd4e36f619a59d513a5 | 652cea73b7b7b7c622a2be670e44e3c499c6d49f, 5ea1dcc9418c4e06ce29ed5170596f497ba86872, 5949d339f5ec98752d56dcd4e36f619a59d513a5 |
| Linux/Linuxgeneric | 2.6.32 | Not reported |
| Linux/Linuxgeneric | >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <344e59fc4f2cba6dc04ce5e2a77388645d4ca834 || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <22263d241bad753217d545f8085b7ead52e2873b || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <2003918e13f43cf6c5698be3cc9aa3657dd676a8 || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <29639f00bfa49da7904ba0a499e0da7a0e5d735e || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <261d2b5f4afa0570ca906e553c93811c5abe4590 || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <652cea73b7b7b7c622a2be670e44e3c499c6d49f || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <5ea1dcc9418c4e06ce29ed5170596f497ba86872 || >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <5949d339f5ec98752d56dcd4e36f619a59d513a5 | 344e59fc4f2cba6dc04ce5e2a77388645d4ca834, 22263d241bad753217d545f8085b7ead52e2873b, 2003918e13f43cf6c5698be3cc9aa3657dd676a8, 29639f00bfa49da7904ba0a499e0da7a0e5d735e, 261d2b5f4afa0570ca906e553c93811c5abe4590, 652cea73b7b7b7c622a2be670e44e3c499c6d49f, 5ea1dcc9418c4e06ce29ed5170596f497ba86872, 5949d339f5ec98752d56dcd4e36f619a59d513a5 |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 28, 2026
In the Linux kernel, the following vulnerability has been resolved: perf sched: Fix register_pid() overflow, strcpy, and BUG_ON register_pid() has several issues when processing untrusted perf.data: 1. Integer overflow: (pid + 1) * sizeof(struct task_desc *) can wrap to a small value on 32-bit systems when pid is large (e.g. 0x40000000), causing realloc to return a tiny buffer followed by out-of-bounds writes in the initialization loop. 2. Heap buffer overflow: strcpy(task->comm, comm) copies the untrusted comm string into a fixed 20-byte COMM_LEN buffer with no length check. 3. BUG_ON on allocation failure: perf.data is untrusted input, so allocation failures should be handled gracefully rather than killing the process. 4. Realloc of sched->tasks assigned directly back, leaking the old pointer on failure; nr_tasks incremented before the realloc, leaving corrupted state on failure. Cap pid at PID_MAX_LIMIT (4194304, matching the kernel's maximum on 64-bit), replace strcpy with strlcpy, guard against NULL comm, replace BUG_ON with NULL returns using safe realloc patterns, and add NULL checks in callers that dereference the result.
Quoted source text, attributed separately from HOL analysis.