CVE-2018-5803: Input Validation

Published Mar 2, 2018
·
Updated

An error in the "sctpmakechunk()" function (net/sctp/smmakechunk.c) when handling SCTP packets length can be exploited by a malicious local user to cause a kernel crash and a DoS.

References:

https://packetstormsecurity.com/files/146620/secunia-sctpmakechunkdos.txt

https://marc.info/?t=151818093200004&r=1&w=2

https://marc.info/?t=151818682600001&r=1&w=2

An upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=07f2c7ab6f8d0a7e7c5764c4e6cc9c52951b9d9c

Other sources

In the Linux Kernel before version 4.15.8, 4.14.25, 4.9.87, 4.4.121, 4.1.51, and 3.2.102, an error in the "sctpmakechunk()" function (net/sctp/smmakechunk.c) when handling SCTP packets length can be exploited to cause a kernel crash.

— Ubuntu

Affected Software

39 affected componentsFixes available
Linux Linux kernel<3.2.102
Linux Linux kernel>=3.3<4.1.51
Linux Linux kernel>=4.3<4.9.87
Linux Linux kernel>=4.10<4.14.25
Linux Linux kernel>=4.15<4.15.8
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
redhat Virtualization Host=4.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Workstation=7.0
debian/linux
6.1.176-16.1.190-16.12.107-16.12.116-17.2.15-17.3.3-1
ubuntu/linux<3.13.0-153.203
3.13.0-153.203
ubuntu/linux-aws<4.4.0-1022.22
4.4.0-1022.22
ubuntu/linux-lts-xenial<4.4.0-127.153~14.04.1
4.4.0-127.153~14.04.1
ubuntu/linux<4.4.0-127.153
4.4.0-127.153
ubuntu/linux-aws<4.4.0-1060.69
4.4.0-1060.69
ubuntu/linux-azure<4.15.0-1013.13~16.04.2
4.15.0-1013.13~16.04.2
ubuntu/linux-gcp<4.15.0-1014.14~16.04.1
4.15.0-1014.14~16.04.1
ubuntu/linux-hwe<4.15.0-24.26~16.04.1
4.15.0-24.26~16.04.1
ubuntu/linux-kvm<4.4.0-1026.31
4.4.0-1026.31
ubuntu/linux-oem<4.13.0-1031.35
4.13.0-1031.35
ubuntu/linux-raspi2<4.4.0-1090.98
4.4.0-1090.98
ubuntu/linux-snapdragon<4.4.0-1093.98
4.4.0-1093.98
ubuntu/linux-fips<4.4.0-1008.10
4.4.0-1008.10
ubuntu/linux-azure-fde*
ubuntu/linux-azure-fde-5.15*
ubuntu/linux-gke*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-azure-6.11*
ubuntu/linux-gcp-6.11*
ubuntu/linux-hwe-6.11*
ubuntu/linux-lowlatency-hwe-6.11*
ubuntu/linux-raspi-realtime*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.116-1Fixed in 7.2.15-1Fixed in 7.3.3-1
  2. Upgrade

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

    Fixed in 3.13.0-153.203
  3. Upgrade

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

    Fixed in 4.4.0-1022.22
  4. Upgrade

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

    Fixed in 4.4.0-127.153~14.04.1
  5. Upgrade

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

    Fixed in 4.4.0-127.153
  6. Upgrade

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

    Fixed in 4.4.0-1060.69
  7. Upgrade

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

    Fixed in 4.15.0-1013.13~16.04.2
  8. Upgrade

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

    Fixed in 4.15.0-1014.14~16.04.1
  9. Upgrade

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

    Fixed in 4.15.0-24.26~16.04.1
  10. Upgrade

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

    Fixed in 4.4.0-1026.31
  11. Upgrade

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

    Fixed in 4.13.0-1031.35
  12. Upgrade

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

    Fixed in 4.4.0-1090.98
  13. Upgrade

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

    Fixed in 4.4.0-1093.98
  14. Upgrade

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

    Fixed in 4.4.0-1008.10
  15. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.15.8
  16. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.14.25
  17. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.9.87
  18. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.4.121
  19. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.1.51
  20. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 3.2.102

Event History

Mar 2, 2018
Data Sourced
via Red Hat·04:17 PM
DescriptionSeverityAffected Software
Mar 6, 2018
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software
Jun 12, 2018
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
DescriptionWeakness
Data Sourced
via NVD·04:29 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2018-5803?

CVE-2018-5803 is classified as a high severity vulnerability due to its potential to cause a denial of service through kernel crashes.

2

How do I fix CVE-2018-5803?

To fix CVE-2018-5803, update your system to the latest patched version of the Linux kernel or affected software.

3

Which versions of Linux Kernel are affected by CVE-2018-5803?

CVE-2018-5803 affects Linux Kernel versions prior to 3.2.102 and several versions between 3.3 and 4.15.

4

Can CVE-2018-5803 be exploited remotely?

No, CVE-2018-5803 requires local access to exploit, as it affects handling of SCTP packets.

5

What are the potential impacts of CVE-2018-5803?

The potential impacts of CVE-2018-5803 include system instability and denial of service due to kernel crashes.

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