lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7f024fcd5c97dc70bb9121c80407cf3cf9be7159 · < 46d59ff421824b6483549d87f14efffbbbd1f6cb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
lockd: Plug nlm_file refcount leak on cached nlm_do_fopen() failure
The cached-file path in nlm_lookup_file() reaches the found: label unconditionally, even when nlm_do_fopen() fails. At that label *result and file->f_count are updated before the error is returned. The wrappers nlm3svc_lookup_file() and nlm4svc_lookup_file() then bail out of their switch without copying *result back to their caller, so the proc handler's local nlm_file pointer remains NULL and the cleanup path skips nlm_release_file(). The f_count increment is never released, and nlm_traverse_files() can no longer reap the file because its refcount never returns to zero between requests.
Short-circuit the cached path so neither *result nor f_count is touched when nlm_do_fopen() fails on a hashed nlm_file.
From the CVE record · Linux
A cached-file lookup in the Linux kernel's lockd can leak an nlm_file reference when nlm_do_fopen() fails. Repeated failures can prevent the file from being reaped between requests. The input does not specify authentication or user-interaction requirements.
Teams running the Linux kernel should check their versions; affected versions are not specified.