LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3872: An off-by-one read/write issue was found in the SDHCI device of QEMU.

An off-by-one read/write issue was found in the SDHCI device of QEMU. It occurs when reading/writing the Buffer Data Port Register in sdhci_read_dataport and sdhci_write_dataport, respectively, if data_count == block_size. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-3872 is a QEMU denial-of-service flaw. A malicious guest VM could trigger an off-by-one read/write bug in the emulated SDHCI device and crash the QEMU process on the host. The business impact is service interruption for affected virtualized workloads, not documented data theft or privilege escalation in the supplied sources.

Executive priority

Prioritize remediation for shared virtualization, hosted customer workloads, and systems running untrusted guests. The likely impact is outage of affected virtual machines or services through host-side QEMU process crashes, which can be operationally significant even without evidence of data compromise.

Technical view

The issue is a CWE-193 off-by-one condition in QEMU SDHCI Buffer Data Port Register handling, specifically sdhci_read_dataport and sdhci_write_dataport when data_count equals block_size. The supplied record lists QEMU affected up to latest v7.1.0-rc4 and assigns CVSS 3.1 score 8.6, with high availability impact.

Likely exposure

Exposure is most likely where QEMU, or downstream products embedding QEMU, run affected SDHCI device emulation for guest workloads. The bundle names QEMU and links a NetApp advisory, but it does not enumerate every downstream product, distribution package, or fixed version.

Exploitation context

The source bundle says a malicious guest could crash the QEMU host process. CISA KEV status is false, and the provided sources do not state active exploitation or public weaponization. Treat this as a guest-to-host availability risk requiring access to a vulnerable virtualized environment.

Researcher notes

Evidence supports a high-severity availability flaw in QEMU SDHCI dataport handling. The supplied sources do not provide a fixed version, exploit availability, or complete downstream product matrix. Validate exposure through actual QEMU versions, device configuration, and vendor-specific advisories before declaring risk closed.

Mitigation direction

  • Inventory QEMU deployments and downstream appliances that may embed QEMU.
  • Check QEMU, operating system, and appliance vendor advisories for CVE-2022-3872 fixes.
  • Apply supported vendor updates once the applicable fixed package is identified.
  • Review the NetApp advisory if NetApp products are in scope.
  • Avoid running untrusted guests on affected hosts until vendor guidance is applied.

Validation and detection

  • Confirm whether deployed QEMU versions are up to v7.1.0-rc4.
  • Identify workloads using QEMU SDHCI emulation or affected virtual hardware profiles.
  • Check vendor changelogs or advisories for explicit CVE-2022-3872 remediation.
  • Review host monitoring for unexpected QEMU process crashes.
  • Map NetApp product exposure against the linked NetApp advisory.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-193: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-3872 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H3.94Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2022-3872Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aQEMUAffected: up to latest v7.1.0-rc4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-193 · source CWE mapping

Off-by-one Error

Off-by-one Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.