medium
5.5
CWE
770
Advisory Published
Updated

CVE-2024-50271: signal: restore the override_rlimit logic

First published: Tue Nov 19 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: signal: restore the override_rlimit logic Prior to commit d64696905554 ("Reimplement RLIMIT_SIGPENDING on top of ucounts") UCOUNT_RLIMIT_SIGPENDING rlimit was not enforced for a class of signals. However now it's enforced unconditionally, even if override_rlimit is set. This behavior change caused production issues. For example, if the limit is reached and a process receives a SIGSEGV signal, sigqueue_alloc fails to allocate the necessary resources for the signal delivery, preventing the signal from being delivered with siginfo. This prevents the process from correctly identifying the fault address and handling the error. From the user-space perspective, applications are unaware that the limit has been reached and that the siginfo is effectively 'corrupted'. This can lead to unpredictable behavior and crashes, as we observed with java applications. Fix this by passing override_rlimit into inc_rlimit_get_ucounts() and skip the comparison to max there if override_rlimit is set. This effectively restores the old behavior.

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

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=5.14<6.1.117
Linux Kernel>=6.2<6.6.61
Linux Kernel>=6.7<6.11.8
Linux Kernel=6.12-rc1
Linux Kernel=6.12-rc2
Linux Kernel=6.12-rc3
Linux Kernel=6.12-rc4
Linux Kernel=6.12-rc5
Linux Kernel=6.12-rc6
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

Remedy

https://git.kernel.org/stable/c/012f4d5d25e9ef92ee129bd5aa7aa60f692681e1

Remedy

https://git.kernel.org/stable/c/0208ea17a1e4456fbfe555f13ae5c28f3d671e40

Remedy

https://git.kernel.org/stable/c/4877d9b2a2ebad3ae240127aaa4cb8258b145cf7

Remedy

https://git.kernel.org/stable/c/9e05e5c7ee8758141d2db7e8fea2cab34500c6ed

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

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

    CVE-2024-50271 has a high severity due to the potential for exploitation in the Linux kernel affecting signal handling.

  • How do I fix CVE-2024-50271?

    To fix CVE-2024-50271, update the Linux kernel to a version that includes the patch for this vulnerability.

  • Which versions of the Linux kernel are affected by CVE-2024-50271?

    CVE-2024-50271 affects multiple versions of the Linux kernel between 5.14 and 6.11.8, as well as certain 6.12 release candidates.

  • What types of systems are at risk from CVE-2024-50271?

    Systems running affected versions of the Linux kernel could be at risk due to improper enforcement of the rlimit for signals.

  • Is there a specific mitigation for CVE-2024-50271 if an update cannot be applied?

    Currently, the only effective mitigation for CVE-2024-50271 is to apply the kernel update to ensure the rlimit for signals is enforced properly.

Company

Resources

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