CVE-2024-50059

Description

A flaw was found in the ntb_hw_switchtec component of the Linux kernel. This vulnerability arises from a race condition during the removal of the ntb_hw_switchtec module, where the system attempts to use memory after it has been freed. A local attacker could exploit this timing issue to achieve privilege escalation or execute arbitrary code, leading to a complete compromise of system integrity and confidentiality, as well as denial of service.

Mitigation

To mitigate this issue, prevent the `ntb_hw_switchtec` kernel module from loading if it is not required. This can be done by creating a blacklist file:

1. Create or edit `/etc/modprobe.d/blacklist-ntb_hw_switchtec.conf` and add the following line:
   `blacklist ntb_hw_switchtec`

2. Regenerate the initramfs to ensure the blacklist is applied at boot:
   `dracut -f -v`

3. Reboot the system for the changes to take effect.

Warning: Blacklisting this module may impact functionality if Switchtec NTB hardware is present and in use.

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).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score777.8
Attack VectorLocalLocalLocal
Attack ComplexityHighHighLow
Privileges RequiredLowLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityHighHighHigh
Integrity ImpactHighHighHigh
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

NVD: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.