CVE-2019-20054: Null Pointer Dereference

Published Dec 28, 2019
·
Updated

A flaw was found in the Linux kernel’s implementation of dropping sysctl entries. A local attacker who has access to load modules on the system can trigger a condition during module load failure and panic the system.

Other sources

A flaw was found in the Linux kernels implementation of dropping sysctl entries. The case where insertheader() fails the parent pointer may still be set to null and then accessed.

This operation is usually invoked during a module load (a local, privileged operation) and requires a failure mode to take place. It is unlikely to be able to be used successfully as an attack vector.

Upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23da9588037ecdd4901db76a5b79a42b529c4ec3 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=89189557b47b35683a27c80ee78aef18248eefb4

References:

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.11 https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.6

— Red Hat

In the Linux kernel before 5.0.6, there is a NULL pointer dereference in dropsysctltable() in fs/proc/procsysctl.c, related to putlinks, aka CID-23da9588037e.

Affected Software

64 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1160.rt56.1131.el7
0:3.10.0-1160.rt56.1131.el7
redhat/kernel-alt<0:4.14.0-115.19.1.el7a
0:4.14.0-115.19.1.el7a
redhat/kernel<0:3.10.0-1160.el7
0:3.10.0-1160.el7
redhat/kernel-rt<0:4.18.0-240.rt7.54.el8
0:4.18.0-240.rt7.54.el8
redhat/kernel<0:4.18.0-240.el8
0:4.18.0-240.el8
Linux Linux kernel<5.0.6
NetApp Active Iq Unified Manager Vmware Vsphere
NetApp Cloud Backup
NetApp Data Availability Services
NetApp E-Series SANtricity OS Controller>=11.0<=11.70.2
NetApp Fas\/aff Baseboard Management Controller
NetApp Solidfire \& Hci Management Node
NetApp Steelstore Cloud Integrated Storage
NetApp Solidfire Baseboard Management Controller
NetApp H610s Firmware
NetApp H610s
NetApp 8300 Firmware
NetApp 8300
NetApp 8700 Firmware
NetApp 8700
NetApp A400 Firmware
NetApp A400
ubuntu/linux-aws<4.4.0-1054.58
4.4.0-1054.58
ubuntu/linux-azure<4.15.0-1059.64~14.04.1
4.15.0-1059.64~14.04.1
ubuntu/linux-lts-xenial<4.4.0-164.192~14.04.1
4.4.0-164.192~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-157.185
4.4.0-157.185
ubuntu/linux-aws<4.4.0-1090.101
4.4.0-1090.101
ubuntu/linux-aws-hwe<4.15.0-1047.49~16.04.1
4.15.0-1047.49~16.04.1
ubuntu/linux-azure<4.15.0-1056.61
4.15.0-1056.61
ubuntu/linux-gcp<4.15.0-1041.43
4.15.0-1041.43
ubuntu/linux-hwe<4.15.0-60.67~16.04.1
4.15.0-60.67~16.04.1
ubuntu/linux-kvm<4.4.0-1052.59
4.4.0-1052.59
ubuntu/linux-oracle<4.15.0-1022.25~16.04.1
4.15.0-1022.25~16.04.1
ubuntu/linux-raspi2<4.4.0-1117.126
4.4.0-1117.126
ubuntu/linux-snapdragon<4.4.0-1121.127
4.4.0-1121.127
ubuntu/linux-hwe-edge*
ubuntu/linux-fips<4.4.0-1015.20
4.4.0-1015.20
ubuntu/linux<4.15.0-60.67
4.15.0-60.67
ubuntu/linux-aws<4.15.0-1047.49
4.15.0-1047.49
ubuntu/linux-azure<5.0.0-1014.14~18.04.1
5.0.0-1014.14~18.04.1
ubuntu/linux-gcp<4.15.0-1042.45
4.15.0-1042.45
ubuntu/linux-gke-4.15<4.15.0-1041.43
4.15.0-1041.43
ubuntu/linux-hwe<5.0.0-23.24~18.04.1
5.0.0-23.24~18.04.1
ubuntu/linux-hwe-edge<5.3.0-19.20~18.04.2
5.3.0-19.20~18.04.2
ubuntu/linux-kvm<4.15.0-1043.43
4.15.0-1043.43
ubuntu/linux-oem<4.15.0-1056.65
4.15.0-1056.65
ubuntu/linux-oem-osp1<5.0.0-1015.16
5.0.0-1015.16
ubuntu/linux-oracle<4.15.0-1022.25
4.15.0-1022.25
ubuntu/linux-raspi2<4.15.0-1044.47
4.15.0-1044.47
ubuntu/linux-snapdragon<4.15.0-1062.69
4.15.0-1062.69
ubuntu/linux-azure-edge*
ubuntu/linux-gcp-edge*
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-gke*
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:3.10.0-1160.rt56.1131.el7
  2. Upgrade

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

    Fixed in 0:4.14.0-115.19.1.el7a
  3. Upgrade

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

    Fixed in 0:3.10.0-1160.el7
  4. Upgrade

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

    Fixed in 0:4.18.0-240.rt7.54.el8
  5. Upgrade

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

    Fixed in 0:4.18.0-240.el8
  6. Upgrade

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

    Fixed in 4.4.0-1054.58
  7. Upgrade

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

    Fixed in 4.15.0-1059.64~14.04.1
  8. Upgrade

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

    Fixed in 4.4.0-164.192~14.04.1
  9. Upgrade

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

    Fixed in 4.4.0-157.185
  10. Upgrade

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

    Fixed in 4.4.0-1090.101
  11. Upgrade

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

    Fixed in 4.15.0-1047.49~16.04.1
  12. Upgrade

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

    Fixed in 4.15.0-1056.61
  13. Upgrade

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

    Fixed in 4.15.0-1041.43
  14. Upgrade

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

    Fixed in 4.15.0-60.67~16.04.1
  15. Upgrade

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

    Fixed in 4.4.0-1052.59
  16. Upgrade

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

    Fixed in 4.15.0-1022.25~16.04.1
  17. Upgrade

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

    Fixed in 4.4.0-1117.126
  18. Upgrade

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

    Fixed in 4.4.0-1121.127
  19. Upgrade

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

    Fixed in 4.4.0-1015.20
  20. Upgrade

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

    Fixed in 4.15.0-60.67
  21. Upgrade

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

    Fixed in 4.15.0-1047.49
  22. Upgrade

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

    Fixed in 5.0.0-1014.14~18.04.1
  23. Upgrade

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

    Fixed in 4.15.0-1042.45
  24. Upgrade

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

    Fixed in 4.15.0-1041.43
  25. Upgrade

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

    Fixed in 5.0.0-23.24~18.04.1
  26. Upgrade

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

    Fixed in 5.3.0-19.20~18.04.2
  27. Upgrade

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

    Fixed in 4.15.0-1043.43
  28. Upgrade

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

    Fixed in 4.15.0-1056.65
  29. Upgrade

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

    Fixed in 5.0.0-1015.16
  30. Upgrade

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

    Fixed in 4.15.0-1022.25
  31. Upgrade

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

    Fixed in 4.15.0-1044.47
  32. Upgrade

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

    Fixed in 4.15.0-1062.69
  33. Upgrade

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

    Fixed in 4.15.0-2018.18
  34. Upgrade

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

    Fixed in 4.15.0-2006.7
  35. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 5.0.6

Event History

Dec 28, 2019
CVE Published
12:00 AM
CVE Published
via MITRE·04:07 AM
Data Sourced
via MITRE·04:07 AM
Description
Data Sourced
via OSV·05:15 AM
DescriptionSeverityAffected Software
Jan 11, 2020
Data Sourced
via Red Hat·03:16 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2019-20054?

CVE-2019-20054 is a vulnerability in the Linux kernel that allows a local attacker to panic the system by triggering a condition during module load failure.

2

How severe is CVE-2019-20054?

CVE-2019-20054 has a severity rating of 5.1 (medium).

3

Which versions of the Linux kernel are affected by CVE-2019-20054?

Versions of the Linux kernel before 5.0.6 are affected by CVE-2019-20054.

4

How can I fix CVE-2019-20054?

To fix CVE-2019-20054, update your Linux kernel to version 5.0.6 or later.

5

Where can I find more information about CVE-2019-20054?

More information about CVE-2019-20054 can be found at the following references: [Reference 1], [Reference 2], [Reference 3].

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