IxgbenApplication · VMware
CVE-2022-36797
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 · uneditedProtection mechanism failure in the Intel(R) Ethernet 500 Series Controller drivers for VMware before version 1.10.0.1 may allow an authenticated user to potentially enable 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 · high confidenceThe Intel(R) Ethernet 500 Series Controller drivers for VMware contain a protection mechanism failure that allows an authenticated local user to potentially cause a denial of service. This vulnerability affects versions prior to 1.10.0.1.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
< 1.10.0.1CVSS 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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Ixgben driver is presentOn the ESXi host, run 'vmkload_mod -l | grep ixgben' or check /usr/lib/vmware/vmkmod/ for the ixgben module fileAffected if The Ixgben driver module is not found on the system, then this CVE does not apply
-
Check the installed Ixgben driver versionRun 'vmkload_mod -s ixgben' or use 'esxcli system module get -m ixgben' to retrieve the driver version informationAffected if The displayed version is less than 1.10.0.1 (for example, 1.9.x or earlier)
-
Verify the driver is actively in useRun 'esxcli network nic list' or 'vmkload_mod -l | grep ixgben' to confirm the driver is loaded and bound to network interfacesAffected if The driver is loaded and running, and its version is below 1.10.0.1
A system is affected if the Ixgben driver for Intel Ethernet 500 Series Controller is installed with a version lower than 1.10.0.1.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.10.0.1
Update the Intel Ethernet 500 Series Controller drivers for VMware to version 1.10.0.1 or later to remediate this vulnerability.
1.10.0.1
- Identify the current version of the Ixgben driver installed in the VMware environment
- Obtain the Intel(R) Ethernet 500 Series Controller driver package version 1.10.0.1 or later from Intel's official support channels
- Apply the driver update through VMware's standard driver update process, which typically involves updating VMware Tools or installing the updated driver bundle
- Reboot the affected virtual machine or host system as required by the driver installation
- Verify the installed driver version is 1.10.0.1 or later using system utilities such as 'vmkload_mod -s ixgben' or through VMware's esxcli command
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ixgben
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36797 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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