Homepage
About Snyk

Memory Leak Affecting kernel-64k-debug-modules package, versions <0:5.14.0-427.33.1.el9_4

Severity

 Recommended
high

Based on AlmaLinux 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 ID SNYK-ALMALINUX9-KERNEL64KDEBUGMODULES-8339006
  • published 4 Nov 2024
  • disclosed 28 Aug 2024
Report a new vulnerability Found a mistake?

Introduced: 28 Aug 2024

CVE-2024-42152 Open this link in a new tab
CWE-401 Open this link in a new tab

How to fix?

Upgrade AlmaLinux:9 kernel-64k-debug-modules to version 0:5.14.0-427.33.1.el9_4 or higher.
This issue was patched in ALSA-2024:5928.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-64k-debug-modules package and not the kernel-64k-debug-modules package as distributed by AlmaLinux. See How to fix? for AlmaLinux:9 relevant fixed versions and status.

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

nvmet: fix a possible leak when destroy a ctrl during qp establishment

In nvmet_sq_destroy we capture sq->ctrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl->sqs and sq->ctrl (for nvme-loop primarily), and drop the final reference on the ctrl.

However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But before kill_and_confirm of sq->ref (i.e. the admin connect managed to get an sq live reference). In this case, sq->ctrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl.

Solve this by re-capturing the sq->ctrl after all inflight request has completed, where for sure sq->ctrl reference is final, and move forward based on that.

This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window.

References

CVSS Scores

version 3.1
Expand this section

NVD

4.7 medium
  • Attack Vector (AV)
    Local
  • Attack Complexity (AC)
    High
  • Privileges Required (PR)
    Low
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    None
  • Integrity (I)
    None
  • Availability (A)
    High
Expand this section

Red Hat

4.4 medium
Expand this section

SUSE

5.5 medium