CWE
476
Advisory Published
CVE Published
Updated

CVE-2024-42089: ASoC: fsl-asoc-card: set priv->pdev before using it

First published: Mon Jul 29 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: ASoC: fsl-asoc-card: set priv->pdev before using it priv->pdev pointer was set after being used in fsl_asoc_card_audmux_init(). Move this assignment at the start of the probe function, so sub-functions can correctly use pdev through priv. fsl_asoc_card_audmux_init() dereferences priv->pdev to get access to the dev struct, used with dev_err macros. As priv is zero-initialised, there would be a NULL pointer dereference. Note that if priv->dev is dereferenced before assignment but never used, for example if there is no error to be printed, the driver won't crash probably due to compiler optimisations.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=3.18<4.19.317
Linux Kernel>=4.20<5.4.279
Linux Kernel>=5.5<5.10.221
Linux Kernel>=5.11<5.15.162
Linux Kernel>=5.16<6.1.97
Linux Kernel>=6.2<6.6.37
Linux Kernel>=6.7<6.9.8
Linux Kernel=6.10-rc1
Linux Kernel=6.10-rc2
Linux Kernel=6.10-rc3
Linux Kernel=6.10-rc4
Linux Kernel=6.10-rc5
debian/linux
5.10.223-1
5.10.234-1
6.1.123-1
6.1.128-1
6.12.12-1
6.12.17-1
debian/linux-6.1
6.1.128-1~deb11u1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-42089?

    CVE-2024-42089 is considered a medium severity vulnerability affecting the Linux kernel.

  • How do I fix CVE-2024-42089?

    To fix CVE-2024-42089, upgrade to the patched versions of the Linux kernel, namely 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.11-1, or 6.12.12-1.

  • Which Linux kernel versions are affected by CVE-2024-42089?

    CVE-2024-42089 affects multiple kernel versions, specifically those from 3.18 up to 6.10-rc5.

  • Is CVE-2024-42089 exploited in the wild?

    As of now, there are no public reports indicating that CVE-2024-42089 has been actively exploited in the wild.

  • What are the consequences of not addressing CVE-2024-42089?

    Ignoring CVE-2024-42089 may expose affected systems to potential vulnerabilities that could lead to privilege escalation or other security risks.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203