CVE-2019-11152
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 adjacent 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 before version 21.40 allow a privileged user to potentially achieve privilege escalation, cause denial of service, or disclose information through adjacent network access.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 Intel WiFi adapter in systemWindows: Open Device Manager, expand 'Network adapters' and look for Intel wireless devices (Ax201, Ax200, AC9560, AC9462, AC9461, AC9260, 8265, 8260). Linux: Run 'lspci | grep -i intel' or 'iw list' to list wireless devices.Affected if The system has one of the affected Intel WiFi adapters listed in the CVE (Ax201, Ax200, AC9560, AC9462, AC9461, AC9260, 8265, or 8260)
-
Check current firmware versionWindows: In Device Manager, right-click the Intel wireless adapter, select 'Properties', go to 'Driver' tab, click 'Driver Details' or check firmware version in 'Details' tab under 'Firmware version'. Linux: Run 'iw dev wlan0 info' or check '/sys/class/net/wlan0/device/firmware_version' if available.Affected if Unable to retrieve firmware version from the wireless adapter
-
Compare firmware version to 21.40Compare the installed firmware version number to 21.40. Note that version format may vary (e.g., 21.40.0, 21.40.1, etc.). Any version before 21.40.x is affected.Affected if The installed firmware version is less than 21.40 (for example, 20.x, 19.x, or any version starting with a number lower than 21.40)
The system is affected if it contains an Intel WiFi adapter from the affected product list and the installed firmware version is lower than 21.40.
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
Update Intel WiFi drivers to version 21.40 or later to remediate the memory corruption issues.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11152 — 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-11152 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