CVE-2024-50294
Description
A flaw was found in the Linux kernel. A local user can cause a Denial of Service (DoS) due to missing locking in the RxRPC network protocol subsystem. When a queued client call is aborted before being processed, improper synchronization allows a race condition that can corrupt the pending call queue and cause connection requests to hang indefinitely.
Mitigation
To mitigate this vulnerability on systems that do not use the in-kernel AFS filesystem or RxRPC protocol, prevent the rxrpc kernel module from loading:
1. Create a modprobe configuration file to disable autoloading:
# echo "install rxrpc /bin/true" > /etc/modprobe.d/disable-rxrpc.conf
2. If the module is currently loaded, unload it:
# modprobe -r rxrpc
Caveats:
Disabling rxrpc prevents the use of the AF_RXRPC socket family and the in-kernel AFS client (kafs). If the module is currently in use and cannot be unloaded dynamically, a system reboot is required for the change to take full effect.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | 4.7 | 7.8 |
| Attack Vector | Local | Local | Local |
| Attack Complexity | Low | High | Low |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | None | High |
| Integrity Impact | None | None | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Availability
Technical Impact: Modify Application Data; DoS: Instability; DoS: Crash, Exit, or Restart
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.