CVE-2016-8105
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 · uneditedDrivers for the Intel Ethernet Controller X710 and Intel Ethernet Controller XL710 families before version 22.0 are vulnerable to a denial of service in certain layer 2 network configurations.
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 · moderate confidenceIntel Ethernet Controller X710 and XL710 firmware/drivers before version 22.0 contain a denial of service vulnerability triggered by specific layer 2 network configurations. The vulnerability allows remote attackers to cause network connectivity loss by exploiting certain switched network environments.
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<= 21.3<= 21.3CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/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 Intel X710/XL710 network hardwareRun 'lspci | grep -i intel' or check device manager for Intel X710 or XL710 Ethernet controllersAffected if No Intel X710 or XL710 network devices are present in the system
-
Check installed driver version on LinuxRun 'ethtool -i <interface>' or check '/sys/class/net/<interface>/device/driver' for the driver version. Example: ethtool -i eth0Affected if Driver version is 21.3 or lower, or version cannot be determined but matches <=21.3 pattern
-
Check installed driver version on WindowsOpen Device Manager, expand Network adapters, right-click Intel X710/XL710 device, select Properties > Driver tab, note the driver versionAffected if Driver version displays as 21.3.x or lower
-
Verify layer 2 network configurationCheck if the network is configured in switched layer 2 environment. Inspect switch port configuration, VLAN settings, and whether the adapter is using bridging or switch virtualization featuresAffected if System operates in a switched layer 2 network with specific configurations that trigger the vulnerability (exact config varies by environment)
A user is affected if they have Intel X710 or XL710 hardware running driver version 21.3 or lower AND operate in a switched layer 2 network environment.
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.
From vendor dataUpdate Intel Ethernet Controller X710/XL710 firmware and drivers to version 22.0 or later. Test network stability in the affected layer 2 configuration after applying the update.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8105 — 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-2016-8105 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