CVE-2018-13053: Integer Overflow

Published Jul 2, 2018
·
Updated

A flaw was found in the alarmtimernsleep() function in kernel/time/alarmtimer.c in the Linux kernel. The ktimeaddsafe() function is not used and an integer overflow can happen causing an alarm not to fire or possibly a denial-of-service if using a large relative timeout.

References:

https://bugzilla.kernel.org/showbug.cgi?id=200303

An upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f936e19cc0ef97dbe3a56e9498922ad5ba1edef

Other sources

The alarmtimernsleep function in kernel/time/alarmtimer.c in the Linux kernel through 4.17.3 has an integer overflow via a large relative timeout because ktimeaddsafe is not used.

— Ubuntu

Affected Software

44 affected componentsFixes available
Linux Linux kernel<=4.17.3
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Debian Debian Linux=8.0
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-1
ubuntu/linux-aws<4.4.0-1034.37
4.4.0-1034.37
ubuntu/linux-lts-xenial<4.4.0-139.165~14.04.1
4.4.0-139.165~14.04.1
ubuntu/linux-azure<4.15.0-1059.64~14.04.1
4.15.0-1059.64~14.04.1
ubuntu/linux*
ubuntu/linux<4.4.0-139.165
4.4.0-139.165
ubuntu/linux-aws<4.4.0-1072.82
4.4.0-1072.82
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-1055.60
4.15.0-1055.60
ubuntu/linux-gcp<4.15.0-1040.42~16.04.1
4.15.0-1040.42~16.04.1
ubuntu/linux-hwe<4.15.0-58.64~16.04.1
4.15.0-58.64~16.04.1
ubuntu/linux-kvm<4.4.0-1037.43
4.4.0-1037.43
ubuntu/linux-oracle<4.15.0-1021.23~16.04.1
4.15.0-1021.23~16.04.1
ubuntu/linux-raspi2<4.4.0-1100.108
4.4.0-1100.108
ubuntu/linux-snapdragon<4.4.0-1104.109
4.4.0-1104.109
ubuntu/linux-fips<4.4.0-1008.10
4.4.0-1008.10
ubuntu/linux<4.15.0-58.64
4.15.0-58.64
ubuntu/linux-aws<4.15.0-1047.49
4.15.0-1047.49
ubuntu/linux-azure<4.18.0-1011.11~18.04.1
4.18.0-1011.11~18.04.1
ubuntu/linux-gcp<4.15.0-1040.42
4.15.0-1040.42
ubuntu/linux-gke-4.15<4.15.0-1040.42
4.15.0-1040.42
ubuntu/linux-kvm<4.15.0-1042.42
4.15.0-1042.42
ubuntu/linux-oem<4.15.0-1050.57
4.15.0-1050.57
ubuntu/linux-oracle<4.15.0-1021.23
4.15.0-1021.23
ubuntu/linux-raspi2<4.15.0-1043.46
4.15.0-1043.46
ubuntu/linux-snapdragon<4.15.0-1060.66
4.15.0-1060.66
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-raspi2*
ubuntu/linux-riscv*
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 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1
  2. Upgrade

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

    Fixed in 4.4.0-1034.37
  3. Upgrade

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

    Fixed in 4.4.0-139.165~14.04.1
  4. Upgrade

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

    Fixed in 4.15.0-1059.64~14.04.1
  5. Upgrade

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

    Fixed in 4.4.0-139.165
  6. Upgrade

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

    Fixed in 4.4.0-1072.82
  7. Upgrade

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

    Fixed in 4.15.0-1047.49~16.04.1
  8. Upgrade

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

    Fixed in 4.15.0-1055.60
  9. Upgrade

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

    Fixed in 4.15.0-1040.42~16.04.1
  10. Upgrade

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

    Fixed in 4.15.0-58.64~16.04.1
  11. Upgrade

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

    Fixed in 4.4.0-1037.43
  12. Upgrade

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

    Fixed in 4.15.0-1021.23~16.04.1
  13. Upgrade

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

    Fixed in 4.4.0-1100.108
  14. Upgrade

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

    Fixed in 4.4.0-1104.109
  15. Upgrade

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

    Fixed in 4.4.0-1008.10
  16. Upgrade

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

    Fixed in 4.15.0-58.64
  17. Upgrade

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

    Fixed in 4.15.0-1047.49
  18. Upgrade

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

    Fixed in 4.18.0-1011.11~18.04.1
  19. Upgrade

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

    Fixed in 4.15.0-1040.42
  20. Upgrade

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

    Fixed in 4.15.0-1040.42
  21. Upgrade

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

    Fixed in 4.15.0-1042.42
  22. Upgrade

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

    Fixed in 4.15.0-1050.57
  23. Upgrade

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

    Fixed in 4.15.0-1021.23
  24. Upgrade

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

    Fixed in 4.15.0-1043.46
  25. Upgrade

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

    Fixed in 4.15.0-1060.66
  26. Upgrade

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

    Fixed in 4.15.0-2018.18
  27. Upgrade

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

    Fixed in 4.15.0-2006.7
  28. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch 5f936e19cc0ef97dbe3a56e9498922ad5ba1edef

Event History

Jul 2, 2018
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·12:00 PM
Data Sourced
via MITRE·12:00 PM
Description
Data Sourced
via NVD·12:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 3, 2018
Data Sourced
via Red Hat·02:42 PM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2018-13053?

CVE-2018-13053 has a high severity due to its potential to cause denial-of-service from integer overflow.

2

How do I fix CVE-2018-13053?

To fix CVE-2018-13053, update the Linux kernel to a version that includes the necessary patches, such as 5.10.223-1 or newer.

3

What versions of Linux are affected by CVE-2018-13053?

CVE-2018-13053 affects Linux kernel versions up to and including 4.17.3 and specific Ubuntu and Debian releases.

4

Can CVE-2018-13053 lead to remote code execution?

CVE-2018-13053 does not lead to remote code execution directly but can cause denial-of-service conditions.

5

What component of the Linux kernel does CVE-2018-13053 affect?

CVE-2018-13053 affects the alarm_timer_nsleep() function in the Linux kernel's alarm timer implementation.

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