CVE-2026-93231
Received Received - Intake

Lockd Argument Swap in Linux Kernel

Vulnerability report for CVE-2026-93231, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: lockd: fix swapped arguments in nlmsvc_match_ip() When releasing locks by server IP address via /proc/fs/nfsd/unlock_ip, nlmsvc_unlock_all_by_ip() calls nlm_traverse_files() with the server sockaddr as the opaque @data argument: nlm_traverse_files(server_addr, nlmsvc_match_ip, NULL); The match callback is later invoked from nlm_traverse_locks() as: match(lockhost, host); where the first argument is the nlm_host that owns the lock, and the second argument is the @data that was originally passed down (here the server sockaddr). This is the convention every other match callback relies on (nlmsvc_mark_host(), nlmsvc_same_host(), nlmsvc_is_client()): arg1 is the real nlm_host, arg2 is the caller-supplied reference value. nlmsvc_match_ip() has had these two arguments reversed ever since the unlock-by-IP feature was introduced in commit 4373ea84c84d ("lockd: unlock lockd locks associated with a given server ip"): return rpc_cmp_addr(nlm_srcaddr(host), datap); Here @host is actually the server sockaddr, so nlm_srcaddr(host) dereferences a struct sockaddr as a struct nlm_host and reads garbage at the offset of h_srcaddr; meanwhile @datap is actually the lock owner's nlm_host but is compared as a sockaddr. As a result the comparison practically never matches and locks are not released for the requested IP. Swap the arguments so the lock owner's source address is compared against the requested server address: return rpc_cmp_addr(nlm_srcaddr(datap), (struct sockaddr *)host); [ cel: fix the misleading typedef parameter names too ]

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-09-25
AI Q&A
2026-09-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a bug in the lockd component where arguments in a function call are swapped. The function nlmsvc_match_ip() was designed to compare a lock owner's address with a requested server address to release locks. However, the arguments were reversed, causing the comparison to fail and locks not being released for the requested IP address.

Detection Guidance

This vulnerability affects the Linux kernel's lockd component and may prevent proper release of NFS locks by IP address. Detection requires checking kernel logs for lockd errors or verifying if locks are not being released correctly after /proc/fs/nfsd/unlock_ip operations. No specific commands are provided in the context.

Impact Analysis

This vulnerability could lead to locks not being properly released on a server when requested via /proc/fs/nfsd/unlock_ip. This might cause resource leaks or unexpected behavior in NFS (Network File System) operations, potentially disrupting file access or causing performance issues.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a Linux kernel issue related to lock release functionality in NFS server operations, which does not involve data processing, storage, or access controls that these regulations typically address.

Mitigation Strategies

Apply the kernel patch that fixes the argument swap in nlmsvc_match_ip(). Update to a patched kernel version. Restart NFS services after applying the fix to ensure proper lock management.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-93231. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart