CVE-2024-50271

signal: restore the override_rlimit logic

State
Published
Severity
5.5 Medium
Published
Nov 19, 2024
Updated
May 11, 2026
Reserved
Oct 21, 2024

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.15.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HCISA-ADP

Weaknesses

  • CWE-770 Allocation of Resources Without Limits or Throttling

Affected Products

ProductVersions
LinuxLinux
  • d64696905554e919321e31afc210606653b8f6a4 to before 012f4d5d25e9ef92ee129bd5aa7aa60f692681e1Affected
  • d64696905554e919321e31afc210606653b8f6a4 to before 4877d9b2a2ebad3ae240127aaa4cb8258b145cf7Affected
  • d64696905554e919321e31afc210606653b8f6a4 to before 0208ea17a1e4456fbfe555f13ae5c28f3d671e40Affected
  • d64696905554e919321e31afc210606653b8f6a4 to before 9e05e5c7ee8758141d2db7e8fea2cab34500c6edAffected
LinuxLinux
  • 5.14Affected
  • before 5.14Not affected
  • 6.1.117 through 6.1.*Not affected
  • 6.6.61 through 6.6.*Not affected
  • 6.11.8 through 6.11.*Not affected
  • 6.12 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.