CVE-2026-23052 Details
Description
In the Linux kernel, the following vulnerability has been resolved: ftrace: Do not over-allocate ftrace memory The pg_remaining calculation in ftrace_process_locs() assumes that ENTRIES_PER_PAGE multiplied by 2^order equals the actual capacity of the allocated page group. However, ENTRIES_PER_PAGE is PAGE_SIZE / ENTRY_SIZE (integer division). When PAGE_SIZE is not a multiple of ENTRY_SIZE (e.g. 4096 / 24 = 170 with remainder 16), high-order allocations (like 256 pages) have significantly more capacity than 256 * 170. This leads to pg_remaining being underestimated, which in turn makes skip (derived from skipped - pg_remaining) larger than expected, causing the WARN(skip != remaining) to trigger. Extra allocated pages for ftrace: 2 with 654 skipped WARNING: CPU: 0 PID: 0 at kernel/trace/ftrace.c:7295 ftrace_process_locs+0x5bf/0x5e0 A similar problem in ftrace_allocate_records() can result in allocating too many pages. This can trigger the second warning in ftrace_process_locs(). Extra allocated pages for ftrace WARNING: CPU: 0 PID: 0 at kernel/trace/ftrace.c:7276 ftrace_process_locs+0x548/0x580 Use the actual capacity of a page group to determine the number of pages to allocate. Have ftrace_allocate_pages() return the number of allocated pages to avoid having to calculate it. Use the actual page group capacity when validating the number of unused pages due to skipped entries. Drop the definition of ENTRIES_PER_PAGE since it is no longer used.
A vulnerability in the Linux kernel's ftrace functionality can lead to memory over-allocation. The issue arises because the calculation of remaining pages in the ftrace process locations function underestimates the actual capacity of allocated pages, especially when the page size is not a multiple of the entry size. This miscalculation can cause the ftrace system to skip more entries than it should, triggering warnings about the discrepancy. The problem can also occur in another ftrace function responsible for allocating records, potentially leading to further warnings about skipped entries.
Users can upgrade to the patched version of the Linux kernel available in the Linux kernel stable tree.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Feb 4, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/23936d19e4383c8dfb03931f032473d4baf92533 | kernel.org | |
| https://git.kernel.org/stable/c/9aef476717994e96dadfb359641c4b82b521aa36 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/be55257fab181b93af38f8c4b1b3cb453a78d742 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/bf802b936a7b269917e4dc233e49f6a928db8286 | kernel.org |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Feb 4, 2026 | New CVE Received | kernel.org |
Volerion