CVE-2018-20788
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/leds/leds-aw2023.c in the led driver for custom Linux kernels on the Xiaomi Redmi 6pro daisy-o-oss phone has several integer overflows because of a left-shifting operation when the right-hand operand can be equal to or greater than the integer length. This can be exploited by a crafted application for denial of service.
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 confidenceThe leds-aw2023.c LED driver in custom Linux kernels for the Xiaomi Redmi 6pro contains integer overflow vulnerabilities caused by left-shift operations where the shift amount can equal or exceed the integer bit width. A crafted application can trigger these overflows to cause denial of service.
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<= 2018-11-26CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 if leds-aw2023 driver is presentCheck /sys/class/leds/ for aw2023 device entries, or run 'lsmod | grep aw2023' to see if the module is loadedAffected if The aw2023 LED driver module is loaded or device nodes referencing aw2023 exist in /sys/class/leds/
-
Determine kernel build dateRun 'uname -a' to see kernel version string, or check '/proc/version' for build timestampAffected if Kernel build date is on or before November 26, 2018 (2018-11-26)
-
Confirm driver source file presenceCheck if drivers/leds/leds-aw2023.c exists in the kernel source tree by running 'find /lib/modules -name leds-aw2023*' 2>/dev/nullAffected if The driver source or compiled module exists in the kernel
-
Check for LED trigger configurationExamine /sys/class/leds/ for any LED devices that may be using the aw2023 driver, and check their 'trigger' file contentsAffected if LED devices are registered and using the aw2023 driver with any trigger configuration
You are affected if the leds-aw2023 driver is loaded on a Micode Xiaomi Perseus P Oss kernel built on or before 2018-11-26, as the integer overflow vulnerability exists in that specific driver and kernel combination.
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 dataThe fix requires adding proper bounds validation on shift operations in the driver to ensure the shift amount is always less than the integer bit width, along with using safer integer types where appropriate.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20788 — 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-2018-20788 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