Linux KernelOperating system · Linux
CVE-2018-20510
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 · uneditedThe print_binder_transaction_ilocked function in drivers/android/binder.c in the Linux kernel 4.14.90 allows local users to obtain sensitive address information by reading "*from *code *flags" lines in a debugfs file.
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 print_binder_transaction_ilocked function in drivers/android/binder.c in Linux kernel 4.14.90 exposes sensitive kernel memory addresses through debugfs output. When local users read the binder debugfs file, the function prints '*from *code *flags' lines containing memory addresses that could aid in developing exploits for other kernel vulnerabilities.
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
Linux KernelOperating system
= 4.14.90CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify the exact kernel version is 4.14.90Run `uname -r` or check `/proc/version` to get the running kernel versionAffected if The kernel version is exactly 4.14.90
-
Confirm the Android binder driver is enabledCheck if the binder module is loaded with `lsmod | grep binder` or verify CONFIG_ANDROID_BINDER_IPC is set in `/boot/config-$(uname -r)` or `/proc/config.gz`Affected if The binder driver is compiled into the kernel or loaded as a module
-
Verify debugfs is mounted and accessibleRun `mount | grep debugfs` or check if `/sys/kernel/debug` exists and is accessibleAffected if debugfs is mounted and readable by the local user
-
Check for binder debugfs entriesLook for binder-related files in debugfs, typically under `/sys/kernel/debug/binder/` or `/d/binder/` when debugfs is mountedAffected if The binder debugfs directory exists and is readable by the user
-
Inspect binder debugfs output for exposed memory addressesRead files in the binder debugfs directory (e.g., `cat /sys/kernel/debug/binder/transactions` or similar) and search for hexadecimal memory address patternsAffected if The output contains lines with kernel memory addresses in the format shown in the vulnerability description (addresses visible in '*from *code *flags' style output)
A user is affected if running exactly kernel 4.14.90 with the binder driver enabled and accessible debugfs interface, where reading binder debugfs files exposes kernel memory addresses.
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 dataRestrict or disable access to the binder debugfs interface, or upgrade to a kernel version that patches this information disclosure vulnerability.
Fix this in Linux Kernel
Scoped from the published advisory
- 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-2018-20510 — 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-20510 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