Vulnerability · Published Sep 24, 2026 · Assigned by Linux

CVE-2026-93231lockd: fix swapped arguments in nlmsvc_match_ip()

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 92.6% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

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

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-93231
Debian:13linux6.12.113-1DEBIAN-CVE-2026-93231
Debian:14linux7.2.6-1DEBIAN-CVE-2026-93231
Debian:12linux-6.126.12.113-1~deb12u1DEBIAN-CVE-2026-93231
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-93231
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-93231
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-93231
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-93231

Affected products (as reported)

VendorProductVersions
Linux Linux 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before e7124d223c5a2dfb4c1a7b2eea24375edc355a104373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before 68282cbc197b280711f66c4cf05165f911785bcc4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before cfbf21d21aea1a83d5ff38d50466a655e0a6a31d4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before 4fe2db296c9cd897dd1fe06cc0ae9cbc13beefc54373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before d34c2ac447fe0490ede828e0143e2cbcb59e6c774373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before 0d72e78c9d38d5377a059a4837f82b65b91cdcf64373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before 21bcb609e0ab1dd60f39ca3498f85808933bcc9f4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – before b9060689f49dc663e9a3d069c4a65ff63a836e66
Linux Linux 2.6.26

References