ipvs: fix WARNING in ip_vs_app_net_cleanup()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 457c4cbc5a3dde259d2a1f15d5f9785290397267 · < 5663ed63adb9619c98ab7479aa4606fa9b7a548c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipvs: fix WARNING in ip_vs_app_net_cleanup()
During the initialization of ip_vs_app_net_init(), if file ip_vs_app fails to be created, the initialization is successful by default. Therefore, the ip_vs_app file doesn't be found during the remove in ip_vs_app_net_cleanup(). It will cause WRNING.
The following is the stack information: name 'ip_vs_app' WARNING: CPU: 1 PID: 9 at fs/proc/generic.c:712 remove_proc_entry+0x389/0x460 Modules linked in: Workqueue: netns cleanup_net RIP: 0010:remove_proc_entry+0x389/0x460 Call Trace: <TASK> ops_exit_list+0x125/0x170 cleanup_net+0x4ea/0xb00 process_one_work+0x9bf/0x1710 worker_thread+0x665/0x1080 kthread+0x2e4/0x3a0 ret_from_fork+0x1f/0x30 </TASK>
From the CVE record · Linux
In the Linux kernel, IPVS initialization can report success even when creation of the ip_vs_app file fails. Subsequent network namespace cleanup then triggers a kernel warning; the input does not describe an attacker action or specify access or interaction requirements.
Engineers running Linux kernels with IPVS should check their versions; affected versions are not specified.