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


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.21% (10th 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-KERNELLIVEPATCH61851120162-20856447
  • published13 Oct 2026
  • disclosed11 Sept 2026

Introduced: 11 Sep 2026

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

How to fix?

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

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6.18.51-120.162 package and not the kernel-livepatch-6.18.51-120.162 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:

lockd: fix NULL dereference on lockowner allocation failure

nlmclnt_locks_init_private() installs NLM file lock operations even when nlmclnt_find_lockowner() fails to allocate a lockowner. nlmclnt_proc() then returns -ENOMEM, but the VFS still tears down the partially initialized file_lock and calls locks_release_private().

That invokes nlmclnt_locks_release_private(), which dereferences fl->fl_u.nfs_fl.owner and crashes because the owner was never installed.

Clear fl_ops before attempting to initialize the NLM private state, and install the NLM lock operations only after a lockowner has been allocated successfully.

CVSS Base Scores

version 3.1