CVE-2022-49918 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: ipvs: fix WARNING in __ip_vs_cleanup_batch() During the initialization of ip_vs_conn_net_init(), if file ip_vs_conn or ip_vs_conn_sync fails to be created, the initialization is successful by default. Therefore, the ip_vs_conn or ip_vs_conn_sync file doesn't be found during the remove. The following is the stack information: name 'ip_vs_conn_sync' WARNING: CPU: 3 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> __ip_vs_cleanup_batch+0x7d/0x120 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>

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-02-25	0.03%	0.05%	+0.02%
2	2025-11-13	0.10%	0.03%	-0.07%
3	2025-07-01	—	0.10%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-02-25

0.03%

0.05%

+0.02%

2025-11-13

0.10%

0.03%

-0.07%

2025-07-01

—

0.10%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-49918

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49918 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-49918
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49918
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-49918/
`ubuntu`	medium	CVE-2022-49918 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 152, ignored 149, not-affected 100, needed 4, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49918

Affected software / configurations for CVE-2022-49918

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 2.6.39, < 4.19.265	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.224	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.154	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.78	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.8	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc1::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc2::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc3::::::

References for CVE-2022-49918

URL	Tags
https://git.kernel.org/stable/c/3d00c6a0da8ddcf75213e004765e4a42acc71d5d	Patch
https://git.kernel.org/stable/c/5ee2d6b726b0ce339e36569e5849692f4cf4595e	Patch
https://git.kernel.org/stable/c/7effc4ce3d1434ce6ff286866585a6e905fdbfc1	Patch
https://git.kernel.org/stable/c/931f56d59c854263b32075bfac56fdb3b1598d1b	Patch
https://git.kernel.org/stable/c/e724220b826e008764309d2a1f55a9434a4e1530	Patch
https://git.kernel.org/stable/c/f08ee2aa24c076f81d84e26e213d8c6f4efd9f50	Patch

URL

CVE-2022-49918 | ipvs: fix WARNING in __ip_vs_cleanup_batch()

Exploit prediction scoring system (EPSS) score for CVE-2022-49918

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49918

Weakness enumeration for CVE-2022-49918

OS Trackers for CVE-2022-49918

Affected software / configurations for CVE-2022-49918

References for CVE-2022-49918