CVE-2018-20669: Input Validation

Published Mar 18, 2019
·
Updated

An issue where a provided address with accessok() is not checked was discovered in i915gemexecbuffer2ioctl in drivers/gpu/drm/i915/i915gemexecbuffer.c in the Linux kernel through 4.19.13. A local attacker can craft a malicious IOCTL function call to overwrite arbitrary kernel memory, resulting in a Denial of Service or privilege escalation.

Other sources

In i915gemexecbuffer2ioctl of i915gemexecbuffer.c, there is a possible arbitrary kernel memory write due to a missing validation of a userspace pointer. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

— OSV

Affected Software

48 affected componentsFixes available
Linux Linux kernel>=4.13<4.14.185
Linux Linux kernel>=4.15<4.19.129
Linux Linux kernel>=4.20<5.0
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
NetApp Hci Management Node
NetApp Snapprotect
NetApp Solidfire
NetApp Cn1610 Firmware
NetApp Cn1610
All of the following
NetApp Cn1610 Firmware
NetApp Cn1610
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1
Google Android
android/:linux_kernel:>=:0<:2020-07-05
:2020-07-05
ubuntu/linux-azure<4.15.0-1093.103~14.04.1
4.15.0-1093.103~14.04.1
ubuntu/linux-aws-hwe<4.15.0-1080.84~16.04.1
4.15.0-1080.84~16.04.1
ubuntu/linux-azure<4.15.0-1093.103~16.04.1
4.15.0-1093.103~16.04.1
ubuntu/linux-gcp<4.15.0-1081.92~16.04.1
4.15.0-1081.92~16.04.1
ubuntu/linux-hwe<4.15.0-115.116~16.04.1
4.15.0-115.116~16.04.1
ubuntu/linux-oracle<4.15.0-1051.55~16.04.1
4.15.0-1051.55~16.04.1
ubuntu/linux-hwe-edge*
ubuntu/linux<4.15.0-115.116
4.15.0-115.116
ubuntu/linux-aws<4.15.0-1080.84
4.15.0-1080.84
ubuntu/linux-azure<5.0.0-1014.14~18.04.1
5.0.0-1014.14~18.04.1
ubuntu/linux-azure-4.15<4.15.0-1093.103
4.15.0-1093.103
ubuntu/linux-gcp<5.0.0-1020.20~18.04.1
5.0.0-1020.20~18.04.1
ubuntu/linux-gcp-4.15<4.15.0-1081.92
4.15.0-1081.92
ubuntu/linux-gke-4.15<4.15.0-1067.70
4.15.0-1067.70
ubuntu/linux-hwe<5.0.0-23.24~18.04.1
5.0.0-23.24~18.04.1
ubuntu/linux-kvm<4.15.0-1072.73
4.15.0-1072.73
ubuntu/linux-oem<4.15.0-1094.104
4.15.0-1094.104
ubuntu/linux-oracle<4.15.0-1051.55
4.15.0-1051.55
ubuntu/linux-raspi2<4.15.0-1068.72
4.15.0-1068.72
ubuntu/linux-snapdragon<4.15.0-1084.92
4.15.0-1084.92
ubuntu/linux-aws-fips<4.15.0-2025.25
4.15.0-2025.25
ubuntu/linux-azure-fips<4.15.0-2007.8
4.15.0-2007.8
ubuntu/linux-fips<4.15.0-1039.44
4.15.0-1039.44
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-azure-fde*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-raspi-realtime*
ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Upgrade

    Upgrade android/:linux_kernel: to a version that resolves this vulnerability.

    Fixed in :2020-07-05
  3. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.15.0-1093.103~14.04.1
  4. Upgrade

    Upgrade ubuntu/linux-aws-hwe to a version that resolves this vulnerability.

    Fixed in 4.15.0-1080.84~16.04.1
  5. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 4.15.0-1093.103~16.04.1
  6. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 4.15.0-1081.92~16.04.1
  7. Upgrade

    Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.

    Fixed in 4.15.0-115.116~16.04.1
  8. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 4.15.0-1051.55~16.04.1
  9. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 4.15.0-115.116
  10. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 4.15.0-1080.84
  11. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 5.0.0-1014.14~18.04.1
  12. Upgrade

    Upgrade ubuntu/linux-azure-4.15 to a version that resolves this vulnerability.

    Fixed in 4.15.0-1093.103
  13. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 5.0.0-1020.20~18.04.1
  14. Upgrade

    Upgrade ubuntu/linux-gcp-4.15 to a version that resolves this vulnerability.

    Fixed in 4.15.0-1081.92
  15. Upgrade

    Upgrade ubuntu/linux-gke-4.15 to a version that resolves this vulnerability.

    Fixed in 4.15.0-1067.70
  16. Upgrade

    Upgrade ubuntu/linux-hwe to a version that resolves this vulnerability.

    Fixed in 5.0.0-23.24~18.04.1
  17. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 4.15.0-1072.73
  18. Upgrade

    Upgrade ubuntu/linux-oem to a version that resolves this vulnerability.

    Fixed in 4.15.0-1094.104
  19. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 4.15.0-1051.55
  20. Upgrade

    Upgrade ubuntu/linux-raspi2 to a version that resolves this vulnerability.

    Fixed in 4.15.0-1068.72
  21. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.15.0-1084.92
  22. Upgrade

    Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.

    Fixed in 4.15.0-2025.25
  23. Upgrade

    Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.

    Fixed in 4.15.0-2007.8
  24. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 4.15.0-1039.44

Event History

Mar 18, 2019
CVE Published
via MITRE·04:33 PM
Data Sourced
via MITRE·04:33 PM
Description
Mar 21, 2019
Data Sourced
via OSV·04:00 PM
DescriptionSeverityAffected Software
Jul 1, 2020
Advisory Published
via OSV·12:00 AM
Jul 6, 2020
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2018-20669?

CVE-2018-20669 has a high severity rating due to the potential for local attackers to exploit the vulnerability to overwrite arbitrary kernel memory.

2

How do I fix CVE-2018-20669?

To fix CVE-2018-20669, upgrade your Linux kernel to version 4.19.14 or later, or apply patches provided by your distribution.

3

Which Linux kernel versions are affected by CVE-2018-20669?

CVE-2018-20669 affects Linux kernel versions through 4.19.13, specifically versions 4.13 to 4.19.129 and also 4.20 to 5.0.

4

Can CVE-2018-20669 be exploited remotely?

No, CVE-2018-20669 requires local access to the system, meaning an attacker must have local user privileges to exploit this vulnerability.

5

What types of systems are vulnerable to CVE-2018-20669?

Systems running vulnerable versions of the Linux kernel, including distributions like Ubuntu and Debian, as well as specific devices like NetApp appliances, are susceptible to CVE-2018-20669.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203