CVE-2022-49917 [High] | Security Vulnerability in Linux Kernel

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>

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.04%	0.18%	+0.14%
2	2025-11-13	0.10%	0.04%	-0.06%
3	2025-07-01	—	0.10%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.04%

0.18%

+0.14%

2025-11-13

0.10%

0.04%

-0.06%

2025-07-01

—

0.10%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2022-49917

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49917 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-49917
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2022-49917
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-49917/
`ubuntu`	medium	CVE-2022-49917 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-49917

Affected software / configurations for CVE-2022-49917

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 2.6.24, < 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-49917

URL	Tags
https://git.kernel.org/stable/c/06d7596d18725f1a93cf817662d36050e5afb989	Patch
https://git.kernel.org/stable/c/2c8d81bdb2684d53d6cedad7410ba4cf9090e343	Patch
https://git.kernel.org/stable/c/5663ed63adb9619c98ab7479aa4606fa9b7a548c	Patch
https://git.kernel.org/stable/c/8457a00c981fe1a799ce34123908856b0f5973b8	Patch
https://git.kernel.org/stable/c/97f872b00937f2689bff2dab4ad9ed259482840f	Patch
https://git.kernel.org/stable/c/adc76740ccd52e4a1d910767cd1223e134a7078b	Patch

URL

CVE-2022-49917 | ipvs: fix WARNING in ip_vs_app_net_cleanup()

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

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

Weakness enumeration for CVE-2022-49917

OS Trackers for CVE-2022-49917

Affected software / configurations for CVE-2022-49917

References for CVE-2022-49917