Linux Kernel up to 5.10.225/5.15.166/6.1.109/6.6.50/6.10.9 Function Call kernel/locking/mutex.c get_c0_compare_int comparison

Summaryinfo

A vulnerability labeled as problematic has been found in Linux Kernel up to 5.10.225/5.15.166/6.1.109/6.6.50/6.10.9. This issue affects the function get_c0_compare_int of the file kernel/locking/mutex.c of the component Function Call Handler. Executing a manipulation can lead to comparison. This vulnerability is tracked as CVE-2024-46832. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 5.10.225/5.15.166/6.1.109/6.6.50/6.10.9. This vulnerability affects the function get_c0_compare_int of the file kernel/locking/mutex.c of the component Function Call Handler. The manipulation with an unknown input leads to a comparison vulnerability. The CWE definition for the vulnerability is CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: MIPS: cevt-r4k: Don't call get_c0_compare_int if timer irq is installed This avoids warning: [ 0.118053] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283 Caused by get_c0_compare_int on secondary CPU. We also skipped saving IRQ number to struct clock_event_device *cd as it's never used by clockevent core, as per comments it's only meant for "non CPU local devices".

The advisory is available at git.kernel.org. This vulnerability was named CVE-2024-46832 since 09/11/2024. The exploitation appears to be easy. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 208099 (Debian dsa-5782 : affs-modules-6.1.0-21-4kc-malta-di - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.226, 5.15.167, 6.1.110, 6.6.51 or 6.10.10 eliminates this vulnerability. Applying the patch d3ff0f98a52f/e6cd871627ab/b1d2051373bf/32ee0520159f/189d3ed3b25b/50f2b98dc83d is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (208099) and CERT Bund (WID-SEC-2024-3050). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Google Container-Optimized OS
• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• Kyocera Printer
• RESF Rocky Linux
• Broadcom Brocade SANnav
• Open Source Linux Kernel
• IBM QRadar SIEM
• SolarWinds Security Event Manager

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.10.225
• 5.15.166
• 6.1.109
• 6.6.0
• 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.6.16
• 6.6.17
• 6.6.18
• 6.6.19
• 6.6.20
• 6.6.21
• 6.6.22
• 6.6.23
• 6.6.24
• 6.6.25
• 6.6.26
• 6.6.27
• 6.6.28
• 6.6.29
• 6.6.30
• 6.6.31
• 6.6.32
• 6.6.33
• 6.6.34
• 6.6.35
• 6.6.36
• 6.6.37
• 6.6.38
• 6.6.39
• 6.6.40
• 6.6.41
• 6.6.42
• 6.6.43
• 6.6.44
• 6.6.45
• 6.6.46
• 6.6.47
• 6.6.48
• 6.6.49
• 6.6.50
• 6.10.0
• 6.10.1
• 6.10.2
• 6.10.3
• 6.10.4
• 6.10.5
• 6.10.6
• 6.10.7
• 6.10.8
• 6.10.9

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion