CVE-2018-9568
What it is
In sk_clone_lock of sock.c, there is a possible memory corruption due to type confusion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-113509306. References: Upstream kernel.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.8% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.8% · EPSS, next 30 days
- Weakness
- CWE-704
- Record status
- Modified
Affected
- Google Android
- Canonical Ubuntu Linux 12.04
- Canonical Ubuntu Linux 14.04
- Redhat Enterprise Linux Desktop 7.0
- Redhat Enterprise Linux Server 7.0
- Redhat Enterprise Linux Server Aus 7.6
- Redhat Enterprise Linux Server Eus 7.6
- Redhat Enterprise Linux Server Tus 7.6
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-9568.md and follow it. Check whether this project is affected by CVE-2018-9568. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://source.android.com/security/bulletin/2018-12-01
- https://source.android.com/security/bulletin/2018-12-01
References
- https://access.redhat.com/errata/RHSA-2019:0512
- https://access.redhat.com/errata/RHSA-2019:0514
- https://access.redhat.com/errata/RHSA-2019:2696
- https://access.redhat.com/errata/RHSA-2019:2730
- https://access.redhat.com/errata/RHSA-2019:2736
- https://access.redhat.com/errata/RHSA-2019:3967
- https://access.redhat.com/errata/RHSA-2019:4056
- https://access.redhat.com/errata/RHSA-2019:4159
- https://access.redhat.com/errata/RHSA-2019:4164
- https://access.redhat.com/errata/RHSA-2019:4255
- https://source.android.com/security/bulletin/2018-12-01
- https://usn.ubuntu.com/3880-1/
- https://usn.ubuntu.com/3880-2/
- https://access.redhat.com/errata/RHSA-2019:0512
- https://access.redhat.com/errata/RHSA-2019:0514
- https://access.redhat.com/errata/RHSA-2019:2696
- https://access.redhat.com/errata/RHSA-2019:2730
- https://access.redhat.com/errata/RHSA-2019:2736
- https://access.redhat.com/errata/RHSA-2019:3967
- https://access.redhat.com/errata/RHSA-2019:4056
- https://access.redhat.com/errata/RHSA-2019:4159
- https://access.redhat.com/errata/RHSA-2019:4164
- https://access.redhat.com/errata/RHSA-2019:4255
- https://source.android.com/security/bulletin/2018-12-01
- https://usn.ubuntu.com/3880-1/