dbcve.org
IxgbenApplication · VMware

CVE-2022-21793

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-18
Fix available
A fix is available. Upgrade to 1.11.4.0 / 2.1.5.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insufficient control flow management in the Intel(R) Ethernet 500 Series Controller drivers for VMWare before version 1.11.4.0 and in the Intel(R) Ethernet 700 Series Controller drivers for VMWare before version 2.1.5.0 may allow an authenticated user to potentially enable a denial of service via local access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IxgbenApplication
Affected:< 1.11.4.0
I40enApplication
Affected:< 2.1.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.11.4.0 / 2.1.5.0 or later
Fixed in 1.11.4.02.1.5.0
Vendor patch www.intel.com →
Recommended fix High confidence

Ixgben: upgrade to version 1.11.4.0 or later; I40en: upgrade to version 2.1.5.0 or later

  1. Identify the currently installed Intel driver version by running 'vmkmod_info ixgben' or 'vmkmod_info i40en' in ESXi shell, or via VMware vSphere Client under Host > Configure > Storage Drivers
  2. Download the Intel Ethernet 500 Series Controller driver version 1.11.4.0 or later for Ixgben from VMware's driver website or Intel's support portal
  3. Download the Intel Ethernet 700 Series Controller driver version 2.1.5.0 or later for I40en from VMware's driver website or Intel's support portal
  4. Upload the driver VIB file to the ESXi host datastore via Datastore Browser or SCP
  5. Put the ESXi host into maintenance mode from vSphere Client or via 'esxcli system maintenanceMode set --enable true'
  6. Install the new driver using 'esxcli software vib install -v /path/to driver.vib --no-sig-check'
  7. Reboot the ESXi host to load the new driver
  8. Verify the installed driver version using 'vmkmod_info ixgben' or 'vmkmod_info i40en'
Caveat Driver updates in ESXi may require host reboot and should be tested in a staging environment before production deployment; ensure VMotion compatibility and check VMware Hardware Compatibility List

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21793 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data