CVE-2026-89485

Description

A flaw was found in the lockd component of the Linux kernel. This use-after-free vulnerability occurs in the nlm_traverse_files() function when a file's memory is prematurely released while an iterator still holds a pointer to it. A remote attacker could potentially exploit this to cause system instability or a denial of service (DoS) by triggering a concurrent file release during a specific unlock window.

Statement

A race in lockd nlm_traverse_files can dereference a freed nlm_file object because the iterator pins the current file but not the saved next file while dropping nlm_file_mutex around nlm_inspect_file. A concurrent nlm_release_file can unlink and kfree that next object during the unlock window, leaving the iterator to access freed slab memory on the next loop step. For the CVSS the PR:N is used in the paranoid score because an exposed NFS lockd service may be reachable by a remote client without a local account on the target, although reliable triggering still requires NFS/NLM access and a race window. The issue is network reachable when lockd is exposed to untrusted or semi trusted NFS clients. Impact is at least denial of service via kernel crash, and in the worst case may allow confidentiality or integrity impact due to UAF based memory corruption. NFS and lockd are usually deployed inside trusted storage or data center networks rather than the public Internet, but exposure to untrusted clients should be treated as high risk.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.9N/A9.8
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.