CVE-2020-0431: Medium severity Google Android vulnerability

Published Sep 17, 2020
·
Updated

A flaw out of bounds write in the Linux kernel human interface devices subsystem was found in the way user calls find key code by index. A local user could use this flaw to crash the system or escalate privileges on the system.

Other sources

In kbdkeycode of keyboard.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-144161459

References: https://android.googlesource.com/kernel/common/+/cb0a3edf8d00 https://source.android.com/security/bulletin/pixel/2020-09-01

— Red Hat

Affected Software

59 affected componentsFixes available
redhat/kernel-rt<0:4.18.0-305.rt7.72.el8
0:4.18.0-305.rt7.72.el8
redhat/kernel<0:4.18.0-305.el8
0:4.18.0-305.el8
Google Android
openSUSE Leap=15.1
openSUSE Leap=15.2
ubuntu/linux-aws<4.4.0-1062.66
4.4.0-1062.66
ubuntu/linux-azure<4.15.0-1074.79~14.04.1
4.15.0-1074.79~14.04.1
ubuntu/linux-lts-xenial<4.4.0-174.204~14.04.1
4.4.0-174.204~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-174.204
4.4.0-174.204
ubuntu/linux-aws<4.4.0-1102.113
4.4.0-1102.113
ubuntu/linux-aws-hwe<4.15.0-1063.67~16.04.1
4.15.0-1063.67~16.04.1
ubuntu/linux-azure<4.15.0-1075.80
4.15.0-1075.80
ubuntu/linux-gcp<4.15.0-1058.62
4.15.0-1058.62
ubuntu/linux-hwe<4.15.0-91.92~16.04.1
4.15.0-91.92~16.04.1
ubuntu/linux-kvm<4.4.0-1066.73
4.4.0-1066.73
ubuntu/linux-oracle<4.15.0-1035.38~16.04.1
4.15.0-1035.38~16.04.1
ubuntu/linux-raspi2<4.4.0-1129.138
4.4.0-1129.138
ubuntu/linux-snapdragon<4.4.0-1133.141
4.4.0-1133.141
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1029.34
4.4.0-1029.34
ubuntu/linux-fips*
ubuntu/linux<4.15.0-91.92
4.15.0-91.92
ubuntu/linux-aws<4.15.0-1063.67
4.15.0-1063.67
ubuntu/linux-gke-4.15<4.15.0-1055.58
4.15.0-1055.58
ubuntu/linux-gke-5.0<5.0.0-1032.33
5.0.0-1032.33
ubuntu/linux-gke-5.3<5.3.0-1014.15~18.04.1
5.3.0-1014.15~18.04.1
ubuntu/linux-hwe<5.3.0-42.34~18.04.1
5.3.0-42.34~18.04.1
ubuntu/linux-kvm<4.15.0-1056.57
4.15.0-1056.57
ubuntu/linux-oem<4.15.0-1076.86
4.15.0-1076.86
ubuntu/linux-oem-osp1<5.0.0-1043.48
5.0.0-1043.48
ubuntu/linux-oracle<4.15.0-1035.39
4.15.0-1035.39
ubuntu/linux-raspi2<4.15.0-1057.61
4.15.0-1057.61
ubuntu/linux-raspi2-5.3<5.3.0-1019.21~18.04.1
5.3.0-1019.21~18.04.1
ubuntu/linux-snapdragon<4.15.0-1074.81
4.15.0-1074.81
ubuntu/linux-aws-5.0*
ubuntu/linux-aws-5.3*
ubuntu/linux-azure*
ubuntu/linux-azure-5.3*
ubuntu/linux-azure-edge*
ubuntu/linux-gcp*
ubuntu/linux-gcp-5.3*
ubuntu/linux-gcp-edge*
ubuntu/linux-hwe-edge*
ubuntu/linux-oracle-5.0*
ubuntu/linux-oracle-5.3*
ubuntu/linux-aws-fips<4.15.0-2018.18
4.15.0-2018.18
ubuntu/linux-azure-fips<4.15.0-2006.7
4.15.0-2006.7
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-azure-fde*
ubuntu/linux-azure-fde-5.15<5.15.0-1114.123~20.04.1
5.15.0-1114.123~20.04.1
ubuntu/linux-gke*
ubuntu/linux-raspi2*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-raspi-realtime*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel-rt to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-305.rt7.72.el8
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 0:4.18.0-305.el8
  3. Upgrade

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

    Fixed in 4.4.0-1062.66
  4. Upgrade

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

    Fixed in 4.15.0-1074.79~14.04.1
  5. Upgrade

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

    Fixed in 4.4.0-174.204~14.04.1
  6. Upgrade

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

    Fixed in 4.4.0-174.204
  7. Upgrade

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

    Fixed in 4.4.0-1102.113
  8. Upgrade

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

    Fixed in 4.15.0-1063.67~16.04.1
  9. Upgrade

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

    Fixed in 4.15.0-1075.80
  10. Upgrade

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

    Fixed in 4.15.0-1058.62
  11. Upgrade

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

    Fixed in 4.15.0-91.92~16.04.1
  12. Upgrade

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

    Fixed in 4.4.0-1066.73
  13. Upgrade

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

    Fixed in 4.15.0-1035.38~16.04.1
  14. Upgrade

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

    Fixed in 4.4.0-1129.138
  15. Upgrade

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

    Fixed in 4.4.0-1133.141
  16. Upgrade

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

    Fixed in 4.4.0-1029.34
  17. Upgrade

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

    Fixed in 4.15.0-91.92
  18. Upgrade

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

    Fixed in 4.15.0-1063.67
  19. Upgrade

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

    Fixed in 4.15.0-1055.58
  20. Upgrade

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

    Fixed in 5.0.0-1032.33
  21. Upgrade

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

    Fixed in 5.3.0-1014.15~18.04.1
  22. Upgrade

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

    Fixed in 5.3.0-42.34~18.04.1
  23. Upgrade

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

    Fixed in 4.15.0-1056.57
  24. Upgrade

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

    Fixed in 4.15.0-1076.86
  25. Upgrade

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

    Fixed in 5.0.0-1043.48
  26. Upgrade

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

    Fixed in 4.15.0-1035.39
  27. Upgrade

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

    Fixed in 4.15.0-1057.61
  28. Upgrade

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

    Fixed in 5.3.0-1019.21~18.04.1
  29. Upgrade

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

    Fixed in 4.15.0-1074.81
  30. Upgrade

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

    Fixed in 4.15.0-2018.18
  31. Upgrade

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

    Fixed in 4.15.0-2006.7
  32. Upgrade

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

    Fixed in 5.15.0-1114.123~20.04.1

Event History

Sep 17, 2020
CVE Published
via MITRE·06:45 PM
Data Sourced
via MITRE·06:45 PM
DescriptionWeakness
Data Sourced
via OSV·07:15 PM
DescriptionSeverityAffected Software
Jan 25, 2021
Data Sourced
via Red Hat·11:26 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2020-0431?

CVE-2020-0431 is considered a high severity vulnerability that could lead to system crashes or privilege escalation.

2

How do I fix CVE-2020-0431?

To address CVE-2020-0431, ensure that your system is updated to kernel version 4.18.0-305.rt7.72.el8 or 4.18.0-305.el8.

3

Who is affected by CVE-2020-0431?

CVE-2020-0431 affects systems running specific versions of the Linux kernel, including those from Red Hat and openSUSE.

4

What kind of systems are vulnerable to CVE-2020-0431?

Vulnerable systems include certain versions of the Linux kernel used in Red Hat, openSUSE, and Google Android.

5

Can CVE-2020-0431 be exploited remotely?

CVE-2020-0431 requires local access to the system for exploitation, making it less likely to be exploited remotely.

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