NULL Pointer Dereference Affecting kernel-livepatch-6.18.20-20.229 package, versions <1:1.0-0.amzn2023


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.12% (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-KERNELLIVEPATCH6182020229-16348962
  • published3 May 2026
  • disclosed25 Mar 2026

Introduced: 25 Mar 2026

CVE-2026-23309  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

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

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6.18.20-20.229 package and not the kernel-livepatch-6.18.20-20.229 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: Add NULL pointer check to trigger_data_free()

If trigger_data_alloc() fails and returns NULL, event_hist_trigger_parse() jumps to the out_free error path. While kfree() safely handles a NULL pointer, trigger_data_free() does not. This causes a NULL pointer dereference in trigger_data_free() when evaluating data->cmd_ops->set_filter.

Fix the problem by adding a NULL pointer check to trigger_data_free().

The problem was found by an experimental code review agent based on gemini-3.1-pro while reviewing backports into v6.18.y.

CVSS Base Scores

version 3.1