Improper Locking Affecting xen-devel package, versions <4.10.4_34-150000.3.74.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.05% (16th 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 IDSNYK-SLES150-XENDEVEL-2803340
  • published26 Apr 2022
  • disclosed25 Apr 2022

Introduced: 25 Apr 2022

CVE-2022-26356  (opens in a new tab)
CWE-667  (opens in a new tab)

How to fix?

Upgrade SLES:15.0 xen-devel to version 4.10.4_34-150000.3.74.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream xen-devel package and not the xen-devel package as distributed by SLES. See How to fix? for SLES:15.0 relevant fixed versions and status.

Racy interactions between dirty vram tracking and paging log dirty hypercalls Activation of log dirty mode done by XEN_DMOP_track_dirty_vram (was named HVMOP_track_dirty_vram before Xen 4.9) is racy with ongoing log dirty hypercalls. A suitably timed call to XEN_DMOP_track_dirty_vram can enable log dirty while another CPU is still in the process of tearing down the structures related to a previously enabled log dirty mode (XEN_DOMCTL_SHADOW_OP_OFF). This is due to lack of mutually exclusive locking between both operations and can lead to entries being added in already freed slots, resulting in a memory leak.

CVSS Scores

version 3.1