Answer in brief
CVE-2025-71109 records a High severity (CVSS 7.1) vulnerability in MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits. 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.
CVSS is 7.1. 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 | >=e424054000878d7eb11e44289242886d6e219d22 <9cfda98cf02eacfa6b09076e98bd479fd73407c2 || >=e424054000878d7eb11e44289242886d6e219d22 <e3e33ac2eb69d595079a1a1e444c2fb98efdd42d || >=e424054000878d7eb11e44289242886d6e219d22 <7f39b9d0e86ed6236b9a5fb67616ab1f76c4f150 || >=e424054000878d7eb11e44289242886d6e219d22 <36dac9a3dda1f2bae343191bc16b910c603cac25 | 9cfda98cf02eacfa6b09076e98bd479fd73407c2, e3e33ac2eb69d595079a1a1e444c2fb98efdd42d, 7f39b9d0e86ed6236b9a5fb67616ab1f76c4f150, 36dac9a3dda1f2bae343191bc16b910c603cac25 |
| Linux/Linuxgeneric | 2.6.35 | Not reported |
Published upstream
Jan 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
In the Linux kernel, the following vulnerability has been resolved: MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits Since commit e424054000878 ("MIPS: Tracing: Reduce the overhead of dynamic Function Tracer"), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section. This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot. This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.
Quoted source text, attributed separately from HOL analysis.