CVE-2026-80671
N/A
Summary
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:
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.
Heap buffer overflow: strcpy(task->comm, comm) copies the untrusted comm string into a fixed 20-byte COMM_LEN buffer with no length check.
BUG_ON on allocation failure: perf.data is untrusted input, so allocation failures should be handled gracefully rather than killing the process.
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | ec156764d424dd67283c2cd5e9f6f1b8388364ac < 652cea73b7b7b7c622a2be670e44e3c499c6d49f | affected |
| Linux | Linux | ec156764d424dd67283c2cd5e9f6f1b8388364ac < 5ea1dcc9418c4e06ce29ed5170596f497ba86872 | affected |
| Linux | Linux | ec156764d424dd67283c2cd5e9f6f1b8388364ac < 5949d339f5ec98752d56dcd4e36f619a59d513a5 | affected |
| Linux | Linux | 2.6.32 | affected |
| Linux | Linux | 0 < 2.6.32 | unaffected |
| Linux | Linux | 6.18.40 <= 6.18.* | unaffected |
| Linux | Linux | 7.1.5 <= 7.1.* | unaffected |
| Linux | Linux | 7.2 <= * | unaffected |
Weaknesses
References
- https://git.kernel.org/stable/c/652cea73b7b7b7c622a2be670e44e3c499c6d49f
- https://git.kernel.org/stable/c/5ea1dcc9418c4e06ce29ed5170596f497ba86872
- https://git.kernel.org/stable/c/5949d339f5ec98752d56dcd4e36f619a59d513a5
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.