Deadlock Affecting kernel-rt-kvm package, versions *


Severity

0.0
medium
0
10

    Threat Intelligence

    EPSS
    0.04% (9th 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-CENTOS7-KERNELRTKVM-6562621
  • published 4 Apr 2024
  • disclosed 3 Apr 2024

How to fix?

There is no fixed version for Centos:7 kernel-rt-kvm.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-kvm package and not the kernel-rt-kvm package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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

md: Don't suspend the array for interrupted reshape

md_start_sync() will suspend the array if there are spares that can be added or removed from conf, however, if reshape is still in progress, this won't happen at all or data will be corrupted(remove_and_add_spares won't be called from md_choose_sync_action for reshape), hence there is no need to suspend the array if reshape is not done yet.

Meanwhile, there is a potential deadlock for raid456:

  1. reshape is interrupted;

  2. set one of the disk WantReplacement, and add a new disk to the array, however, recovery won't start until the reshape is finished;

  3. then issue an IO across reshpae position, this IO will wait for reshape to make progress;

  4. continue to reshape, then md_start_sync() found there is a spare disk that can be added to conf, mddev_suspend() is called;

Step 4 and step 3 is waiting for each other, deadlock triggered. Noted this problem is found by code review, and it's not reporduced yet.

Fix this porblem by don't suspend the array for interrupted reshape, this is safe because conf won't be changed until reshape is done.

CVSS Scores

version 3.1
Expand this section

Snyk

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

Red Hat

4.4 medium