perf sched: Fix register_pid() overflow, strcpy, and BUG_ON
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2003918e13f43cf6c5698be3cc9aa3657dd676a8, Kernel 22263d241bad753217d545f8085b7ead52e2873b, Kernel 261d2b5f4afa0570ca906e553c93811c5abe4590 and 5 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.32, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <2003918e13f43cf6c5698be3cc9aa3657dd676a8, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <22263d241bad753217d545f8085b7ead52e2873b, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <261d2b5f4afa0570ca906e553c93811c5abe4590, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <29639f00bfa49da7904ba0a499e0da7a0e5d735e, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <344e59fc4f2cba6dc04ce5e2a77388645d4ca834, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <5949d339f5ec98752d56dcd4e36f619a59d513a5, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <5ea1dcc9418c4e06ce29ed5170596f497ba86872, >=ec156764d424dd67283c2cd5e9f6f1b8388364ac <652cea73b7b7b7c622a2be670e44e3c499c6d49f | 2003918e13f43cf6c5698be3cc9aa3657dd676a8, 22263d241bad753217d545f8085b7ead52e2873b, 261d2b5f4afa0570ca906e553c93811c5abe4590, 29639f00bfa49da7904ba0a499e0da7a0e5d735e, 344e59fc4f2cba6dc04ce5e2a77388645d4ca834, 5949d339f5ec98752d56dcd4e36f619a59d513a5, 5ea1dcc9418c4e06ce29ed5170596f497ba86872, 652cea73b7b7b7c622a2be670e44e3c499c6d49f |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket