7.8
CWE
125
Advisory Published
Updated

CVE-2024-50074: parport: Proper fix for array out-of-bounds access

First published: Tue Oct 29 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.

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

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.10.224<5.10.228
Linux Kernel>=5.11<5.15.169
Linux Kernel>=5.16<6.1.114
Linux Kernel>=6.2<6.6.58
Linux Kernel>=6.7<6.11.5
Linux Kernel=6.12-rc1
Linux Kernel=6.12-rc2
Linux Kernel=6.12-rc3
Red Hat Enterprise Linux=8.0
Red Hat Enterprise Linux=9.0
debian/linux<=5.10.223-1<=5.10.226-1
6.1.123-1
6.1.128-1
6.12.12-1
6.12.15-1
debian/linux-6.1
6.1.119-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-50074?

    The severity of CVE-2024-50074 is classified as medium due to potential impacts on system stability.

  • How do I fix CVE-2024-50074?

    To fix CVE-2024-50074, upgrade to the latest version of the Linux kernel that includes the patch for this vulnerability.

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

    CVE-2024-50074 affects Linux kernel versions from 5.10.224 to 5.10.228, 5.11 to 5.15.169, 5.16 to 6.1.114, 6.2 to 6.6.58, 6.7 to 6.11.5, and various release candidates.

  • What are the potential impacts of CVE-2024-50074?

    The potential impacts of CVE-2024-50074 include array out-of-bounds accesses that can lead to information disclosure or system crashes.

  • Is there a workaround for CVE-2024-50074?

    There is no specific workaround recommended for CVE-2024-50074; the best mitigation is to apply the kernel update.

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