CVE-2017-10999
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 · uneditedIn all Qualcomm products with Android releases from CAF using the Linux kernel, concurrent calls into ioctl RMNET_IOCTL_ADD_MUX_CHANNEL in ipa wan driver may lead to memory corruption due to missing locks.
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 confidenceA race condition vulnerability exists in the Qualcomm IPA WAN driver's ioctl handler for RMNET_IOCTL_ADD_MUX_CHANNEL. When multiple threads concurrently invoke this ioctl without proper synchronization, memory corruption occurs due to missing mutex/lock protections in the shared data path.
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<= 8.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Check Android versionRun 'getprop ro.build.version.release' or check Settings > About Phone to determine the Android OS versionAffected if Version is 8.0 or lower (Android 8.0 and earlier are affected)
-
Identify if device uses Qualcomm IPA hardwareCheck kernel boot logs for 'ipa' or 'IPA' references, or check /proc/bootdata for IPA-related firmware filesAffected if Device contains Qualcomm IPA (Integrated Processor for Android) hardware - the vulnerability exists in the IPA WAN driver
-
Verify ipa_wan driver presenceCheck /proc/modules or lsmod output for ipa_wan module, or check /sys/module/ for ipa_wan directoryAffected if The ipa_wan kernel module is present and loaded on the device
-
Confirm rmnet interface availabilityCheck for rmnet network interfaces using 'ip link show' or 'ifconfig -a' - look for interfaces starting with 'rmnet'Affected if rmnet interfaces exist (these trigger the vulnerable RMNET_IOCTL_ADD_MUX_CHANNEL ioctl path)
Device is affected if it runs Android 8.0 or earlier, contains Qualcomm IPA hardware, and has the ipa_wan driver loaded with active rmnet interfaces - the race condition occurs when multiple threads concurrently invoke the RMNET_IOCTL_ADD_MUX_CHANNEL ioctl without proper synchronization.
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 dataApply proper locking (mutex or spinlock) around the mux channel addition logic in the ipa_wan driver to ensure thread-safe access. Validate the fix under concurrent load to confirm the race condition is eliminated.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10999 — 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-2017-10999 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