CVE-2017-18551: Medium severity Linux Linux kernel vulnerability

Published Aug 18, 2019
·
Updated

An issue was discovered in drivers/i2c/i2c-core-smbus.c in the Linux kernel before 4.14.15. There is an out of bounds write in the function i2csmbusxferemulated.

Other sources

An out of bounds (OOB) memory access flaw was found in i2csmbusxferemulated in drivers/i2c/i2c-core-smbus.c in I2C subsystem. A read request for length (data->block[0]) greater than 'I2CSMBUSBLOCKMAX + 1' may cause underlying I2C driver write out of array's boundary. This could allow a local attacker with special user privilege (or root) to crash the system or leak kernel internal information.

Affected Software

30 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.21.2.el7a
0:4.14.0-115.21.2.el7a
redhat/kernel<0:3.10.0-1160.el7
0:3.10.0-1160.el7
redhat/kernel<0:3.10.0-693.81.1.el7
0:3.10.0-693.81.1.el7
redhat/kernel<0:3.10.0-957.65.1.el7
0:3.10.0-957.65.1.el7
redhat/kernel<0:3.10.0-1062.40.1.el7
0:3.10.0-1062.40.1.el7
Linux Linux kernel<4.14.15
openSUSE Leap=15.0
openSUSE Leap=15.1
ubuntu/linux-aws<4.4.0-1054.58
4.4.0-1054.58
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-150.176
4.4.0-150.176
ubuntu/linux-aws<4.4.0-1084.94
4.4.0-1084.94
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-1047.53
4.4.0-1047.53
ubuntu/linux-raspi2<4.4.0-1110.118
4.4.0-1110.118
ubuntu/linux-snapdragon<4.4.0-1114.119
4.4.0-1114.119
ubuntu/linux-fips<4.4.0-1011.14
4.4.0-1011.14
ubuntu/linux-snapdragon<4.15.0-1053.57
4.15.0-1053.57
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*

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.21.2.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 to a version that resolves this vulnerability.

    Fixed in 0:3.10.0-693.81.1.el7
  5. Upgrade

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

    Fixed in 0:3.10.0-957.65.1.el7
  6. Upgrade

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

    Fixed in 0:3.10.0-1062.40.1.el7
  7. Upgrade

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

    Fixed in 4.4.0-1054.58
  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-150.176
  10. Upgrade

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

    Fixed in 4.4.0-1084.94
  11. Upgrade

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

    Fixed in 4.15.0-1013.13~16.04.2
  12. Upgrade

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

    Fixed in 4.15.0-1014.14~16.04.1
  13. Upgrade

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

    Fixed in 4.15.0-24.26~16.04.1
  14. Upgrade

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

    Fixed in 4.4.0-1047.53
  15. Upgrade

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

    Fixed in 4.4.0-1110.118
  16. Upgrade

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

    Fixed in 4.4.0-1114.119
  17. Upgrade

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

    Fixed in 4.4.0-1011.14
  18. Upgrade

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

    Fixed in 4.15.0-1053.57
  19. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.14.15

Event History

Aug 18, 2019
CVE Published
12:00 AM
Aug 19, 2019
CVE Published
via MITRE·01:51 AM
Data Sourced
via MITRE·01:51 AM
Description
Data Sourced
via OSV·02:15 AM
DescriptionSeverityAffected Software
Oct 1, 2019
Data Sourced
via Red Hat·10:39 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2017-18551?

CVE-2017-18551 has a moderate severity level due to the potential for out of bounds memory access.

2

How do I fix CVE-2017-18551?

To mitigate CVE-2017-18551, update to a patched version of the Linux kernel as specified in the vulnerability details.

3

Which versions of the Linux kernel are affected by CVE-2017-18551?

CVE-2017-18551 affects Linux kernel versions prior to 4.14.15.

4

Is CVE-2017-18551 specific to any Linux distribution?

Yes, CVE-2017-18551 impacts various distributions including Red Hat and openSUSE.

5

What component of the Linux kernel is affected by CVE-2017-18551?

CVE-2017-18551 affects the I2C subsystem, specifically the i2c_smbus_xfer_emulated function in the Linux kernel.

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