CVE-2026-99217
In the Linux kernel, the following vulnerability has been resolved: …
In the Linux kernel, the following vulnerability has been resolved: fork: release the files of a failed fork after sched_cancel_fork() Reorder copy_process() cleanup so sched_fork() taking scx_fork_rwsem scx_pre_fork() is safe and isn't held around exiting files. Right now, a fork that fails while another thread closed the bpf link fd will deadlock against its own read side. It also blocks every fork on the system: copy_process() holds scx_fork_rwsem for read exit_files() close_files() filp_close_sync() bpf_scx_unreg() kthread_flush_work() waits for the disable work scx_root_disable() percpu_down_write(&scx_fork_rwsem) Simply release the child's files after sched_cancel_fork() dropped the lock. The task starts out as a copy of its parent so p->files points to the parent's table until copy_files() replaces it. exit_files() must not run for a fork that failed before that. Clear p->files up front so exit_files() is a no-op for those and make copy_files() set it explicitly for CLONE_FILES.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/14c7de6ca239326b79fd3f7aee55dfada1bb72ab
- git.kernel.org/stable/c/27e1cbf8ec5f7117f6bb2d2e44030ac055f09097
- git.kernel.org/stable/c/afa8eb069694bd9f845e5e44eac6e81cbc06780e
- git.kernel.org/stable/c/f7ac8500d58e7684d37403553b1dea90ee2b27b1
- nvd.nist.gov/vuln/detail/CVE-2026-99217
- cve.org/CVERecord?id=CVE-2026-99217
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.