CVE-2023-53075ftrace: Fix invalid address access in lookup_rec() when index is 0
- 7.8HighCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% 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: 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.
Timeline
ID reserved
By Linux
Published
- 18 months later
· 18 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 |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < 2de28e5ce34b22b73b833a21e2c45ae3aade3964
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < 7569ee04b0e3b32df79f64db3a7138573edad9bc
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < ac58b88ccbbb8e9fb83e137cee04a856b1ea6635
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < 83c3b2f4e7c61367c7b24551f4c6eb94bbdda283
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < 2a0d71fabfeb349216d33f001a6421b1768bd3a9
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < 4f84f31f63416b0f02fc146ffdc4ab32723eb7e8
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < f1bd8b7fd890d87d0dc4dedc6287ea34dd07c0b4
- affected 9644302e3315e7e36495d230d5ac7125a316d33e – < ee92fa443358f4fc0017c1d0d325c27b37802504
- affected 3.5
- unaffected < 3.5
- unaffected 4.14.311 – ≤ 4.14.*
- unaffected 4.19.279 – ≤ 4.19.*
- unaffected 5.4.238 – ≤ 5.4.*
- unaffected 5.10.176 – ≤ 5.10.*
- unaffected 5.15.104 – ≤ 5.15.*
- unaffected 6.1.21 – ≤ 6.1.*
- unaffected 6.2.8 – ≤ 6.2.*
- unaffected 6.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/2de28e5ce34b22b73b833a21e2c45ae3aade3964 (opens in a new tab)
- https://git.kernel.org/stable/c/7569ee04b0e3b32df79f64db3a7138573edad9bc (opens in a new tab)
- https://git.kernel.org/stable/c/ac58b88ccbbb8e9fb83e137cee04a856b1ea6635 (opens in a new tab)
- https://git.kernel.org/stable/c/83c3b2f4e7c61367c7b24551f4c6eb94bbdda283 (opens in a new tab)
- https://git.kernel.org/stable/c/2a0d71fabfeb349216d33f001a6421b1768bd3a9 (opens in a new tab)
- https://git.kernel.org/stable/c/4f84f31f63416b0f02fc146ffdc4ab32723eb7e8 (opens in a new tab)
- https://git.kernel.org/stable/c/f1bd8b7fd890d87d0dc4dedc6287ea34dd07c0b4 (opens in a new tab)
- https://git.kernel.org/stable/c/ee92fa443358f4fc0017c1d0d325c27b37802504 (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-2025-13183 (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-2023-53075)Record last updated .