Vulnerability identifier: #VU92045
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 devfreq_monitor(), devfreq_monitor_start() and devfreq_monitor_stop() functions in drivers/devfreq/devfreq.c. A local user can perform a denial of service (DoS) attack.
Mitigation
Install update from vendor's website.
Vulnerable software versions
Linux kernel: 5.10, 5.10 rc1, 5.10 rc2, 5.10 rc3, 5.10 rc4, 5.10 rc5, 5.10 rc7, 5.10.1, 5.10.2, 5.10.3, 5.10.4, 5.10.5, 5.10.6, 5.10.7, 5.10.8, 5.10.9, 5.10.10, 5.10.11, 5.10.12, 5.10.13, 5.10.14, 5.10.15, 5.10.16, 5.10.17, 5.10.18, 5.10.19, 5.10.20, 5.10.21, 5.10.22, 5.10.23, 5.10.24, 5.10.25, 5.10.26, 5.10.27, 5.10.28, 5.10.29, 5.10.30, 5.10.31, 5.10.32, 5.10.33, 5.10.34, 5.10.35, 5.10.36, 5.10.37, 5.10.38, 5.10.39, 5.10.40, 5.10.41, 5.10.42, 5.10.43, 5.10.44, 5.10.45, 5.10.46, 5.10.47, 5.10.48, 5.10.49, 5.10.50, 5.10.51, 5.10.52, 5.10.53, 5.10.54, 5.10.55, 5.10.56, 5.10.57, 5.10.58, 5.10.59, 5.10.60, 5.10.61, 5.10.62, 5.10.63, 5.10.64, 5.10.65, 5.10.66, 5.10.67, 5.10.68, 5.10.69, 5.10.70, 5.10.71, 5.10.72, 5.10.73, 5.10.74, 5.10.75, 5.10.76, 5.10.77, 5.10.78, 5.10.79, 5.10.80, 5.10.81, 5.10.82, 5.10.83, 5.10.84, 5.10.85, 5.10.86, 5.10.87, 5.10.88, 5.10.89, 5.10.90, 5.10.91, 5.10.92, 5.10.93, 5.10.94, 5.10.95, 5.10.96, 5.10.97, 5.10.98, 5.10.99, 5.10.100, 5.10.101, 5.10.102, 5.10.103, 5.10.104, 5.10.105, 5.10.106, 5.10.107, 5.10.108, 5.10.109, 5.10.110, 5.10.111, 5.10.112, 5.10.113, 5.10.114, 5.10.115, 5.10.116, 5.10.117, 5.10.118, 5.10.119, 5.10.120, 5.10.121, 5.10.122, 5.10.123, 5.10.124, 5.10.125, 5.10.126, 5.10.127, 5.10.128, 5.10.129, 5.10.130, 5.10.131, 5.10.132, 5.10.133, 5.10.134, 5.10.135, 5.10.136, 5.10.137, 5.10.138, 5.10.139, 5.10.140, 5.10.141, 5.10.142, 5.10.143, 5.10.144, 5.10.145, 5.10.146, 5.10.147, 5.10.148, 5.10.149, 5.10.150, 5.10.151, 5.10.152, 5.10.153, 5.10.154, 5.10.155, 5.10.156, 5.10.157, 5.10.158, 5.10.159, 5.10.160, 5.10.161, 5.10.162, 5.10.163, 5.10.164, 5.10.165, 5.10.166, 5.10.167, 5.10.168, 5.10.169, 5.10.170, 5.10.171, 5.10.172, 5.10.173, 5.10.174, 5.10.175, 5.10.176, 5.10.177, 5.10.178, 5.10.179, 5.10.180, 5.10.181, 5.10.182, 5.10.183, 5.10.184, 5.10.185, 5.10.186, 5.10.187, 5.10.188, 5.10.189, 5.10.190, 5.10.191, 5.10.192, 5.10.193, 5.10.194, 5.10.195, 5.10.196, 5.10.197, 5.10.198, 5.10.199, 5.10.200, 5.10.201, 5.10.202, 5.10.203, 5.10.204, 5.10.205, 5.10.206, 5.10.207, 5.10.208, 5.10.209, 5.15, 5.15 rc1, 5.15 rc2, 5.15 rc3, 5.15 rc4, 5.15 rc5, 5.15 rc6, 5.15 rc7, 5.15.0, 5.15.1, 5.15.2, 5.15.3, 5.15.4, 5.15.5, 5.15.6, 5.15.7, 5.15.8, 5.15.9, 5.15.10, 5.15.11, 5.15.12, 5.15.13, 5.15.14, 5.15.15, 5.15.16, 5.15.17, 5.15.18, 5.15.19, 5.15.20, 5.15.21, 5.15.22, 5.15.23, 5.15.24, 5.15.25, 5.15.26, 5.15.27, 5.15.28, 5.15.29, 5.15.30, 5.15.31, 5.15.32, 5.15.33, 5.15.34, 5.15.35, 5.15.36, 5.15.37, 5.15.38, 5.15.39, 5.15.40, 5.15.41, 5.15.42, 5.15.43, 5.15.44, 5.15.45, 5.15.46, 5.15.47, 5.15.48, 5.15.49, 5.15.50, 5.15.51, 5.15.52, 5.15.53, 5.15.54, 5.15.55, 5.15.56, 5.15.57, 5.15.58, 5.15.59, 5.15.60, 5.15.61, 5.15.62, 5.15.63, 5.15.64, 5.15.65, 5.15.66, 5.15.67, 5.15.68, 5.15.69, 5.15.70, 5.15.71, 5.15.72, 5.15.73, 5.15.74, 5.15.75, 5.15.76, 5.15.77, 5.15.78, 5.15.79, 5.15.80, 5.15.81, 5.15.82, 5.15.83, 5.15.84, 5.15.85, 5.15.86, 5.15.87, 5.15.88, 5.15.89, 5.15.90, 5.15.91, 5.15.92, 5.15.93, 5.15.94, 5.15.95, 5.15.96, 5.15.97, 5.15.98, 5.15.99, 5.15.100, 5.15.101, 5.15.102, 5.15.103, 5.15.104, 5.15.105, 5.15.106, 5.15.107, 5.15.108, 5.15.109, 5.15.110, 5.15.111, 5.15.112, 5.15.113, 5.15.114, 5.15.115, 5.15.116, 5.15.117, 5.15.118, 5.15.119, 5.15.120, 5.15.121, 5.15.122, 5.15.123, 5.15.124, 5.15.125, 5.15.126, 5.15.127, 5.15.128, 5.15.129, 5.15.130, 5.15.131, 5.15.132, 5.15.133, 5.15.134, 5.15.135, 5.15.136, 5.15.137, 5.15.138, 5.15.139, 5.15.140, 5.15.141, 5.15.142, 5.15.143, 5.15.144, 5.15.145, 5.15.146, 5.15.147, 5.15.148, 6.1, 6.1 rc1, 6.1 rc3, 6.1 rc7, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.1.14, 6.1.15, 6.1.16, 6.1.17, 6.1.18, 6.1.19, 6.1.20, 6.1.21, 6.1.22, 6.1.23, 6.1.24, 6.1.25, 6.1.26, 6.1.27, 6.1.28, 6.1.29, 6.1.30, 6.1.31, 6.1.32, 6.1.33, 6.1.34, 6.1.35, 6.1.36, 6.1.37, 6.1.38, 6.1.39, 6.1.40, 6.1.41, 6.1.42, 6.1.43, 6.1.44, 6.1.45, 6.1.46, 6.1.47, 6.1.48, 6.1.49, 6.1.50, 6.1.51, 6.1.52, 6.1.53, 6.1.54, 6.1.55, 6.1.56, 6.1.57, 6.1.58, 6.1.59, 6.1.60, 6.1.61, 6.1.62, 6.1.63, 6.1.64, 6.1.65, 6.1.66, 6.1.67, 6.1.68, 6.1.69, 6.1.70, 6.1.71, 6.1.72, 6.1.73, 6.1.74, 6.1.75, 6.1.76, 6.6, 6.6 rc1, 6.6 rc2, 6.6 rc3, 6.6 rc4, 6.6 rc5, 6.6 rc6, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 6.6.13, 6.6.14, 6.6.15, 6.7, 6.7 rc1, 6.7 rc2, 6.7 rc3, 6.7 rc5, 6.7 rc6, 6.7 rc7, 6.7.1, 6.7.2, 6.7.3, 6.8 rc1, 6.8 rc2, 6.8 rc5
External links
https://git.kernel.org/stable/c/3399cc7013e761fee9d6eec795e9b31ab0cbe475
https://git.kernel.org/stable/c/099f6a9edbe30b142c1d97fe9a4748601d995675
https://git.kernel.org/stable/c/31569995fc65007b73a3fff605ec2b3401b435e9
https://git.kernel.org/stable/c/0aedb319ef3ed39e9e5a7b7726c8264ca627bbd9
https://git.kernel.org/stable/c/ae815e2fdc284ab31651d52460698bd89c0fce22
https://git.kernel.org/stable/c/aed5ed595960c6d301dcd4ed31aeaa7a8054c0c6
https://mirrors.edge.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.210
https://mirrors.edge.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.149
https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.77
https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.16
https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.7.4
https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.8
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.