CVE-2026-93231lockd: fix swapped arguments in nlmsvc_match_ip()
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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 ]
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 36 days later
· 36 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < e7124d223c5a2dfb4c1a7b2eea24375edc355a10
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < 68282cbc197b280711f66c4cf05165f911785bcc
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < cfbf21d21aea1a83d5ff38d50466a655e0a6a31d
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < 4fe2db296c9cd897dd1fe06cc0ae9cbc13beefc5
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < d34c2ac447fe0490ede828e0143e2cbcb59e6c77
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < 0d72e78c9d38d5377a059a4837f82b65b91cdcf6
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < 21bcb609e0ab1dd60f39ca3498f85808933bcc9f
- affected 4373ea84c84d8a96e99d3da99e813d3e36d1bd11 – < b9060689f49dc663e9a3d069c4a65ff63a836e66
- affected 2.6.26
- unaffected < 2.6.26
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/e7124d223c5a2dfb4c1a7b2eea24375edc355a10 (opens in a new tab)
- https://git.kernel.org/stable/c/68282cbc197b280711f66c4cf05165f911785bcc (opens in a new tab)
- https://git.kernel.org/stable/c/cfbf21d21aea1a83d5ff38d50466a655e0a6a31d (opens in a new tab)
- https://git.kernel.org/stable/c/4fe2db296c9cd897dd1fe06cc0ae9cbc13beefc5 (opens in a new tab)
- https://git.kernel.org/stable/c/d34c2ac447fe0490ede828e0143e2cbcb59e6c77 (opens in a new tab)
- https://git.kernel.org/stable/c/0d72e78c9d38d5377a059a4837f82b65b91cdcf6 (opens in a new tab)
- https://git.kernel.org/stable/c/21bcb609e0ab1dd60f39ca3498f85808933bcc9f (opens in a new tab)
- https://git.kernel.org/stable/c/b9060689f49dc663e9a3d069c4a65ff63a836e66 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86236 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93231)Record last updated .