What happened
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 security weakness in the Linux kernel, the following vulnerability is being tracked as CVE-2026-89485.
CVE-2026-89485 currently carries a CRITICAL 9 8 severity signal in the retained vulnerability data. For an organization using the Linux kernel, the following vulnerability, the next step is to identify affected versions, map where the vulnerable function is reachable and understand what the affected process can access.
The important point is that running an affected version of the Linux kernel, the following vulnerability creates exposure, while an actual compromise still depends on whether the attacker can reach the trigger conditions described above.
Reference sources
Reporting ends here. The sections below are CyberDeltaForce analysis and defender-focused interpretation.
What security teams should do now
- Inventory the affected product deployments and confirm whether the affected component and vulnerable release are present.
- Apply the vendor patch or mitigation for CVE-2026-89485 and validate the affected path after remediation.
What is not yet confirmed
- So far, researchers have not reported exploitation, but that can change as vendor, government or threat-intelligence reporting develops.