CVE-2019-9471
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 set_outbound_iatu of abc-pcie.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-144168326
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 confidenceA missing bounds check in the set_outbound_iatu function of abc-pcie.c (Android kernel PCIe driver) allows a local attacker with System privileges to perform an out-of-bounds write, potentially achieving root privilege escalation.
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 dataall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Confirm the system is running AndroidCheck /proc/version or run 'getprop ro.build.id' or 'uname -a' to verify the OS is AndroidAffected if The system is not Android - this CVE only affects Android kernels
-
Identify the kernel versionRun 'cat /proc/version' or 'uname -r' to retrieve the kernel version stringAffected if Kernel version is earlier than the patched version for A-144168326 (specific patched versions vary by Android release line)
-
Check if abc-pcie driver is presentLook for the driver in /sys/module/ or check kernel config for CONFIG_PCIE_ABC or grep kernel build files for 'abc-pcie.c'Affected if The abc-pcie driver is compiled into the kernel or loaded as a module - the vulnerability exists in this driver code
-
Verify PCIe hardware is presentCheck /sys/bus/pci/devices/ or run 'lspci' (if available) to list PCIe devicesAffected if PCIe devices are enumerated - the set_outbound_iatu function is invoked when PCIe outbound IATU (Address Translation Unit) is configured
-
Check for System-level privilegesDetermine if processes can run with System privilege (uid 1000) - check running processes or examine SELinux domain via 'ps -Z'Affected if System privileges are attainable - the attacker requires System privileges to trigger the vulnerable code path
The system is affected if it runs Android with a kernel containing the abc-pcie driver, has PCIe hardware present, and the kernel version predates the A-144168326 security patch.
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 the Android kernel security patch for A-144168326 which adds proper bounds validation in the set_outbound_iatu function.
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9471 — 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-9471 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