CVE intelligence

CVE-2022-23037

Vulnerability intelligence

Published Mar 10, 2022Sources checked Nov 10, 2026

7.0HIGHCVSS out of 10

What this means

Review the available evidence

CVE-2022-23037 and is rated High severity with a CVSS score of 7.0. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Ubuntu Security Notices guidance

Vendor revision: Nov 10, 2026

Vendor remediation details

This update corrects flaws in the following subsystems: - GPU drivers; - IIO ADC drivers; - Multiple devices driver; - Ethernet bonding driver; - Network drivers; - PCI subsystem; - VFIO drivers; - File systems infrastructure; - F2FS file system; - JFS file system; - Network file system (NFS) server daemon; - OCFS2 file system; - Overlay file system; - Tracing infrastructure; - IUCV driver; (CVE-2021-47633, CVE-2022-49058, CVE-2022-49170, CVE-2023-52784, CVE-2024-53194, CVE-2024-53210, CVE-2024-53214, CVE-2024-56570, CVE-2024-56616, CVE-2024-56763, CVE-2024-56779, CVE-2024-57904, CVE-2025-21664, CVE-2025-38604, CVE-2025-39743, CVE-2026-43456, CVE-2026-74350)

Ubuntu Security Notices guidance

Vendor revision: Nov 10, 2026

Vendor remediation details

CISA KEVNot listedBased on the latest collected catalog

EPSS0.3%Estimated 30-day exploitation probability

Ransomware useNot markedCISA KEV ransomware field

Threat actors0Source-linked actor relationships

Overview

What is CVE-2022-23037?

Linux PV device frontends vulnerable to attacks by backends T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Several Linux PV device frontends are using the grant table interfaces for removing access rights of the backends in ways being subject to race conditions, resulting in potential data leaks, data corruption by malicious backends, and denial of service triggered by malicious backends: blkfront, netfront, scsifront and the gntalloc driver are testing whether a grant reference is still in use.

If this is not the case, they assume that a following removal of the granted access will always succeed, which is not true in case the backend has mapped the granted page between those two operations. As a result the backend can keep access to the memory page of the guest no matter how the page will be used after the frontend I/O has finished.

The xenbus driver has a similar problem, as it doesn't check the success of removing the granted access of a shared ring buffer. blkfront: CVE-2022-23036 netfront: CVE-2022-23037 scsifront: CVE-2022-23038 gntalloc: CVE-2022-23039 xenbus: CVE-2022-23040 blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p, kbdfront, and pvcalls are using a functionality to delay freeing a grant reference until it is no longer in use, but the freeing of the related data page is not synchronized with dropping the granted access.

As a result the backend can keep access to the memory page even after it has been freed and then re-used for a different purpose. CVE-2022-23041 netfront will fail a BUG_ON() assertion if it fails to revoke access in the rx path.

This will result in a Denial of Service (DoS) situation of the guest which can be triggered by the backend. CVE-2022-23042

Source: NVD