lockd: pin next file across nlm_inspect_file lock-drop
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel e999a88133654c6dfc68487fb49da5f20dfa2d4f, Kernel 08a455f87b14c7ff22ae3fdadda62a796a3a5572, Kernel 350087f231c11efcd288c310707c40eab63ca583 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: lockd: pin next file across nlm_inspect_file lock-drop nlm_traverse_files() pins the current file with f_count++ across a mutex_unlock for nlm_inspect_file(), but nothing pins the saved next pointer. A concurrent nlm_release_file() can kfree the next file during the unlock window, and the iterator dereferences freed memory on the next loop step. Pin both current and next before the lock-drop. Advance by swapping the pinned cursors at the end of each iteration so next is always held alive across the unlock. Always call nlm_file_release() after dropping the iteration pin, regardless of whether the file matched the predicate. Use nlm_file_inuse(), which does a live walk of the inode lock list, rather than the cached f_locks field, so skipped files that never ran nlm_inspect_file() are evaluated correctly. Because every file in a hash bucket is now pinned and released, files skipped by the is_failover_file predicate that have no locks, blocks, shares, or external references are deleted during traversal. The old code never evaluated skipped files for cleanup. The new behavior is intentional: such files are stale and should not persist in the table.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <e999a88133654c6dfc68487fb49da5f20dfa2d4f, >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <08a455f87b14c7ff22ae3fdadda62a796a3a5572, >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <350087f231c11efcd288c310707c40eab63ca583, >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <41f0a6d31615fcae261bf28a0aa50050dc93a401, >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <526c49cff3f72c3ec74752016380c7567040581b, >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <550c19222c7132c888e23c9d89079ba1c9bc4cca, >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <c24bdb7df2f34bdc38ca8a73796f5acb40f1830c, >=01df9c5e918ae5559f2d96da0143f8bfbb9e6171 <e3c413f789eaf0170275c7eba523ead73d963f30, =2.6.18 | e999a88133654c6dfc68487fb49da5f20dfa2d4f, 08a455f87b14c7ff22ae3fdadda62a796a3a5572, 350087f231c11efcd288c310707c40eab63ca583, 41f0a6d31615fcae261bf28a0aa50050dc93a401, 526c49cff3f72c3ec74752016380c7567040581b, 550c19222c7132c888e23c9d89079ba1c9bc4cca, c24bdb7df2f34bdc38ca8a73796f5acb40f1830c, e3c413f789eaf0170275c7eba523ead73d963f30 |
| linux-kernel: Kernel | >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.2.0 <6.6.157, >=6.7.0 <6.12.109, >=2.6.18 <5.10.270 | 5.15.221, 6.1.188, 6.18.50, 7.2.4, 6.6.157, 6.12.109, 5.10.270 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket