Expired Pointer Dereference Affecting kernel-livepatch-6.12.103-127.188 package, versions <1:1.0-0.amzn2023


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.13% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-KERNELLIVEPATCH612103127188-19474909
  • published1 Sept 2026
  • disclosed15 Aug 2026

Introduced: 15 Aug 2026

NewCVE-2026-74471  (opens in a new tab)
CWE-825  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 kernel-livepatch-6.12.103-127.188 to version 1:1.0-0.amzn2023 or higher.
This issue was patched in ALAS2023-2026-2110.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6.12.103-127.188 package and not the kernel-livepatch-6.12.103-127.188 package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

tracing: Check return value of __register_event() in trace_module_add_events()

trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event.

If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed.

Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.

CVSS Base Scores

version 3.1