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

12 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
Microsoft azl3 kernel 6.6.47.1-1
Microsoft azl3 kernel 6.6.51.1-1
debian/linux<6.10.9-1
6.10.9-1
debian/linux<6.10.9-1
6.10.9-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Configuration

    Mark get_wq_ctx() as an atomic SMC call instead of a standard SMC call to avoid waitq-context allocation deadlocks.

    Linux kernel firmware: qcom: scm get_wq_ctx() SMC call type = atomic call

Event History

Sep 13, 2024
CVE Published
via MITRE·05:29 AM
Data Sourced
via MITRE·05:29 AM
Description
Data Sourced
via OSV·06:15 AM
DescriptionSeverityAffected Software
Oct 15, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected 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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203