CVE-2019-11151
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 · uneditedMemory corruption issues in Intel(R) WIFI Drivers before version 21.40 may allow a privileged user to potentially enable escalation of privilege, denial of service, and information disclosure 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 confidenceMemory corruption vulnerabilities in Intel WiFi drivers versions prior to 21.40 allow a privileged local user to potentially achieve privilege escalation, cause denial of service, or obtain information disclosure through exploitation of the corrupted memory state.
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.40< 21.40< 21.40< 21.40< 21.40< 21.40< 21.40< 21.40CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the Intel WiFi adapter modelOn Linux, run `lspci | grep -i intel` or `lspci -v | grep -A10 Wireless`. On Windows, open Device Manager, expand Network adapters, and look for Intel WiFi entries. On macOS, run `system_profiler SPNetworkDataType` and look for Wi-Fi or AirPort hardware.Affected if The adapter model matches any of: WiFi 6 Ax201, WiFi 6 Ax200, Wireless AC 9560, Wireless AC 9462, Wireless AC 9461, Wireless AC 9260, Dual Band Wireless AC 8265, or Dual Band Wireless AC 8260.
-
Retrieve the current WiFi firmware versionOn Linux, use `iw list` or check `/sys/class/net/*/device/firmware_version`. On Windows, open Device Manager, right-click the Intel WiFi adapter, select Properties, go to the Driver tab, and look for the firmware version entry, or run `netsh wlan show drivers` and check driver version fields.Affected if A firmware version is displayed that is below 21.40.
-
Confirm the driver version matches firmware versionNote that some tools may report the driver software version rather than the firmware version. Ensure you are checking the firmware version specifically, as the vulnerability is in the firmware component. Cross-reference with Intel PROSet/Wireless tools if available on Windows.Affected if The displayed version is a driver version rather than firmware, or the firmware version cannot be definitively determined.
If the system has any of the listed Intel WiFi adapters and the firmware version is below 21.40, the environment is affected by this CVE.
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 data21.40
Upgrade Intel WiFi drivers to version 21.40 or later to remediate the memory corruption vulnerabilities.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11151 — 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-2019-11151 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