CVE-2025-71109MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits
- 7.1HighCVSS base score
- 0.23%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 10 months later
· 10 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.23% · top 87% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected e424054000878d7eb11e44289242886d6e219d22 – < 3f7a003fe2646337fbc5dd41051ad6754ac34064
- affected e424054000878d7eb11e44289242886d6e219d22 – < 9cfda98cf02eacfa6b09076e98bd479fd73407c2
- affected e424054000878d7eb11e44289242886d6e219d22 – < e3e33ac2eb69d595079a1a1e444c2fb98efdd42d
- affected e424054000878d7eb11e44289242886d6e219d22 – < 7f39b9d0e86ed6236b9a5fb67616ab1f76c4f150
- affected e424054000878d7eb11e44289242886d6e219d22 – < 36dac9a3dda1f2bae343191bc16b910c603cac25
- affected 2.6.35
- unaffected < 2.6.35
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.64 – ≤ 6.12.*
- unaffected 6.18.3 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References5
- https://git.kernel.org/stable/c/3f7a003fe2646337fbc5dd41051ad6754ac34064 (opens in a new tab)
- https://git.kernel.org/stable/c/9cfda98cf02eacfa6b09076e98bd479fd73407c2 (opens in a new tab)
- https://git.kernel.org/stable/c/e3e33ac2eb69d595079a1a1e444c2fb98efdd42d (opens in a new tab)
- https://git.kernel.org/stable/c/7f39b9d0e86ed6236b9a5fb67616ab1f76c4f150 (opens in a new tab)
- https://git.kernel.org/stable/c/36dac9a3dda1f2bae343191bc16b910c603cac25 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-2504 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-71109)Record last updated .