Answer in brief
CVE-2023-53075 records a High severity (CVSS 7.8) vulnerability in ftrace: Fix invalid address access in lookup_rec() when index is 0. 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.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9644302e3315e7e36495d230d5ac7125a316d33e <2de28e5ce34b22b73b833a21e2c45ae3aade3964 || >=9644302e3315e7e36495d230d5ac7125a316d33e <7569ee04b0e3b32df79f64db3a7138573edad9bc || >=9644302e3315e7e36495d230d5ac7125a316d33e <ac58b88ccbbb8e9fb83e137cee04a856b1ea6635 || >=9644302e3315e7e36495d230d5ac7125a316d33e <83c3b2f4e7c61367c7b24551f4c6eb94bbdda283 || >=9644302e3315e7e36495d230d5ac7125a316d33e <2a0d71fabfeb349216d33f001a6421b1768bd3a9 || >=9644302e3315e7e36495d230d5ac7125a316d33e <4f84f31f63416b0f02fc146ffdc4ab32723eb7e8 || >=9644302e3315e7e36495d230d5ac7125a316d33e <f1bd8b7fd890d87d0dc4dedc6287ea34dd07c0b4 || >=9644302e3315e7e36495d230d5ac7125a316d33e <ee92fa443358f4fc0017c1d0d325c27b37802504 | 2de28e5ce34b22b73b833a21e2c45ae3aade3964, 7569ee04b0e3b32df79f64db3a7138573edad9bc, ac58b88ccbbb8e9fb83e137cee04a856b1ea6635, 83c3b2f4e7c61367c7b24551f4c6eb94bbdda283, 2a0d71fabfeb349216d33f001a6421b1768bd3a9, 4f84f31f63416b0f02fc146ffdc4ab32723eb7e8, f1bd8b7fd890d87d0dc4dedc6287ea34dd07c0b4, ee92fa443358f4fc0017c1d0d325c27b37802504 |
| Linux/Linuxgeneric | 3.5 | Not reported |
Published upstream
May 2, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix invalid address access in lookup_rec() when index is 0 KASAN reported follow problem: BUG: KASAN: use-after-free in lookup_rec Read of size 8 at addr ffff000199270ff0 by task modprobe CPU: 2 Comm: modprobe Call trace: kasan_report __asan_load8 lookup_rec ftrace_location arch_check_ftrace_location check_kprobe_address_safe register_kprobe When checking pg->records[pg->index - 1].ip in lookup_rec(), it can get a pg which is newly added to ftrace_pages_start in ftrace_process_locs(). Before the first pg->index++, index is 0 and accessing pg->records[-1].ip will cause this problem. Don't check the ip when pg->index is 0.
Quoted source text, attributed separately from HOL analysis.