CVE-2024-46692: firmware: qcom: scm: Mark get_wq_ctx() as atomic call
Published Sep 13, 2024
·Updated
firmware: qcom: scm: Mark getwqctx() as atomic call
Affected Software
10 affected componentsFixes available
Linux Linux kernel>=6.3<6.6.49
Linux Linux kernel>=6.7<6.10.8
Linux Linux kernel=6.11-rc1
Linux Linux kernel=6.11-rc2
Linux Linux kernel=6.11-rc3
Linux Linux kernel=6.11-rc4
Linux Linux kernel=6.11-rc5
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1
Microsoft azl3 kernel 6.6.47.1-1
Microsoft azl3 kernel 6.6.51.1-1
Remediation
Event History
Sep 13, 2024
CVE Published
via MITRE·05:29 AM
Data Sourced
via MITRE·05:29 AM
Description
Oct 15, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Jan 9, 2025
Data Sourced
via Ubuntu·06:31 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-46692?
CVE-2024-46692 is classified as a high severity vulnerability affecting the Linux kernel.
2
How do I fix CVE-2024-46692?
To fix CVE-2024-46692, update the Linux kernel to one of the patched versions such as 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, or 6.12.11-1.
3
Which versions of the Linux kernel are affected by CVE-2024-46692?
CVE-2024-46692 affects Linux kernel versions from 6.3 to 6.6.49 and certain 6.11 release candidates.
4
What are the implications of CVE-2024-46692?
Exploitation of CVE-2024-46692 could allow a local attacker to manipulate system calls leading to potential denial of service.
5
Is there a workaround for CVE-2024-46692?
Currently, the recommended solution for CVE-2024-46692 is to apply the available kernel updates instead of relying on workarounds.