#VU108302 Improper locking in Linux kernel - CVE-2022-49903
Vulnerability identifier: #VU108302
Vulnerability risk: Low
CVSSv4.0: 4.3 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/U:Clear]
CVE-ID:
CWE-ID:
CWE-667
Exploitation vector: Local
Exploit availability: No
Vulnerable software:
Linux kernel
Operating systems & Components /
Operating system
Vendor: Linux Foundation
Description
The vulnerability allows a local user to perform a denial of service (DoS) attack.
The vulnerability exists due to improper locking within the ip_vs_app_net_init() function in net/netfilter/ipvs/ip_vs_app.c. A local user can perform a denial of service (DoS) attack.
Mitigation
Install update from vendor's website.
Vulnerable software versions
Linux kernel: 4.19, 4.19.1, 4.19.2, 4.19.3, 4.19.4, 4.19.5, 4.19.6, 4.19.7, 4.19.8, 4.19.9, 4.19.10, 4.19.11, 4.19.12, 4.19.13, 4.19.14, 4.19.15, 4.19.16, 4.19.17, 4.19.18, 4.19.19, 4.19.20, 4.19.21, 4.19.22, 4.19.23, 4.19.24, 4.19.25, 4.19.26, 4.19.27, 4.19.28, 4.19.29, 4.19.30, 4.19.31, 4.19.32, 4.19.33, 4.19.34, 4.19.35, 4.19.36, 4.19.37, 4.19.38, 4.19.39, 4.19.40, 4.19.41, 4.19.42, 4.19.43, 4.19.44, 4.19.45, 4.19.46, 4.19.47, 4.19.48, 4.19.49, 4.19.50, 4.19.51, 4.19.52, 4.19.53, 4.19.54, 4.19.55, 4.19.56, 4.19.57, 4.19.58, 4.19.59, 4.19.60, 4.19.61, 4.19.62, 4.19.63, 4.19.64, 4.19.65, 4.19.66, 4.19.67, 4.19.68, 4.19.69, 4.19.70, 4.19.71, 4.19.72, 4.19.73, 4.19.74, 4.19.75, 4.19.76, 4.19.77, 4.19.78, 4.19.79, 4.19.80, 4.19.81, 4.19.82, 4.19.83, 4.19.84, 4.19.85, 4.19.86, 4.19.87, 4.19.88, 4.19.89, 4.19.90, 4.19.91, 4.19.92, 4.19.93, 4.19.94, 4.19.95, 4.19.96, 4.19.97, 4.19.98, 4.19.99, 4.19.100, 4.19.101, 4.19.102, 4.19.103, 4.19.104, 4.19.105, 4.19.106, 4.19.107, 4.19.108, 4.19.109, 4.19.110, 4.19.111, 4.19.112, 4.19.113, 4.19.114, 4.19.115, 4.19.116, 4.19.117, 4.19.118, 4.19.118-2, 4.19.119, 4.19.120, 4.19.121, 4.19.122, 4.19.123, 4.19.124, 4.19.125, 4.19.126, 4.19.127, 4.19.128, 4.19.129, 4.19.130, 4.19.131, 4.19.132, 4.19.133, 4.19.134, 4.19.135, 4.19.136, 4.19.137, 4.19.138, 4.19.139, 4.19.140, 4.19.141, 4.19.142, 4.19.143, 4.19.144, 4.19.145, 4.19.146, 4.19.147, 4.19.148, 4.19.149, 4.19.150, 4.19.151, 4.19.152, 4.19.153, 4.19.154, 4.19.155, 4.19.156, 4.19.157, 4.19.158, 4.19.159, 4.19.160, 4.19.161, 4.19.162, 4.19.163, 4.19.164, 4.19.165, 4.19.166, 4.19.167, 4.19.168, 4.19.169, 4.19.170, 4.19.171, 4.19.172, 4.19.173, 4.19.174, 4.19.175, 4.19.176, 4.19.177, 4.19.178, 4.19.179, 4.19.180, 4.19.181, 4.19.182, 4.19.183, 4.19.184, 4.19.185, 4.19.186, 4.19.187, 4.19.188, 4.19.189, 4.19.190, 4.19.191, 4.19.192, 4.19.193, 4.19.194, 4.19.195, 4.19.196, 4.19.197, 4.19.198, 4.19.199, 4.19.200, 4.19.201, 4.19.202, 4.19.203, 4.19.204, 4.19.205, 4.19.206, 4.19.207, 4.19.208, 4.19.209, 4.19.210, 4.19.211, 4.19.212, 4.19.213, 4.19.214, 4.19.215, 4.19.216, 4.19.217, 4.19.218, 4.19.219, 4.19.220, 4.19.221, 4.19.222, 4.19.223, 4.19.224, 4.19.225, 4.19.226, 4.19.227, 4.19.228, 4.19.229, 4.19.230, 4.19.231, 4.19.232, 4.19.233, 4.19.234, 4.19.235, 4.19.236, 4.19.237, 4.19.238, 4.19.239, 4.19.240, 4.19.241, 4.19.242, 4.19.243, 4.19.244, 4.19.245, 4.19.246, 4.19.247, 4.19.248, 4.19.249, 4.19.250, 4.19.251, 4.19.252, 4.19.253, 4.19.254, 4.19.255, 4.19.256, 4.19.257, 4.19.258, 4.19.259, 4.19.260, 4.19.261, 4.19.262, 4.19.263, 4.19.264
External links
https://git.kernel.org/stable/c/080589287127838046077904f34d5054ea0f895c
https://git.kernel.org/stable/c/0ed71af4d017d2bd2cbb8f7254f613a4914def26
https://git.kernel.org/stable/c/381453770f731f0f43616a1cd4c759b7807a1517
https://git.kernel.org/stable/c/5dbb47ee89762da433cd8458788d7640c85f1a07
https://git.kernel.org/stable/c/768b3c745fe5789f2430bdab02f35a9ad1148d97
https://git.kernel.org/stable/c/83fbf246ced54dadd7b9adc2a16efeff30ba944d
https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.265
Q & A
Can this vulnerability be exploited remotely?
No. This vulnerability can be exploited locally. The attacker should have authentication credentials and successfully authenticate on the system.
Is there known malware, which exploits this vulnerability?
No. We are not aware of malware exploiting this vulnerability.
