Double Free Affecting kernel-rt-debug-devel-matched package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Double Free vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL9-KERNELRTDEBUGDEVELMATCHED-8429108
  • published27 Nov 2024
  • disclosed7 Nov 2024

Introduced: 7 Nov 2024

CVE-2024-50152  (opens in a new tab)
CWE-415  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 kernel-rt-debug-devel-matched.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-debug-devel-matched package and not the kernel-rt-debug-devel-matched package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix possible double free in smb2_set_ea()

Clang static checker(scan-build) warning: fs/smb/client/smb2ops.c:1304:2: Attempt to free released memory. 1304 | kfree(ea); | ^~~~~~~~~

There is a double free in such case: 'ea is initialized to NULL' -> 'first successful memory allocation for ea' -> 'something failed, goto sea_exit' -> 'first memory release for ea' -> 'goto replay_again' -> 'second goto sea_exit before allocate memory for ea' -> 'second memory release for ea resulted in double free'.

Re-initialie 'ea' to NULL near to the replay_again label, it can fix this double free problem.

CVSS Scores

version 3.1