Bug 2363790 (CVE-2023-53075) - CVE-2023-53075 kernel: ftrace: Fix invalid address access in lookup_rec() when index is 0
Summary: CVE-2023-53075 kernel: ftrace: Fix invalid address access in lookup_rec() whe...
Keywords:
Status: NEW
Alias: CVE-2023-53075
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-02 16:05 UTC by OSIDB Bzimport
Modified: 2025-05-05 05:05 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-02 16:05:49 UTC
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.

Comment 1 Avinash Hanwate 2025-05-05 04:59:18 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050215-CVE-2023-53075-6770@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.