CVE-2018-1000204: Medium severity Linux Linux kernel vulnerability

Published Jun 8, 2018
·
Updated

DISPUTED Linux Kernel version 3.18 to 4.16 incorrectly handles an SGIO ioctl on /dev/sg0 with dxferdirection=SGDXFERFROMDEV and an empty 6-byte cmdp. This may lead to copying up to 1000 kernel heap pages to the userspace. This has been fixed upstream in https://github.com/torvalds/linux/commit/a45b599ad808c3c982fdcdc12b0b8611c2f92824 already. The problem has limited scope, as users don't usually have permissions to access SCSI devices. On the other hand, e.g. the Nero user manual suggests doing chmod o+r+w /dev/sg to make the devices accessible. NOTE: third parties dispute the relevance of this report, noting that the requirement for an attacker to have both the CAPSYSADMIN and CAPSYSRAWIO capabilities makes it "virtually impossible to exploit."

Other sources

A malformed SGIO ioctl issued for a SCSI device in the Linux kernel leads to a local kernel data leak manifesting in up to approx. 1000 memory pages copied to the userspace. The problem has limited scope, as non-privileged users usually have no permissions to access SCSI device files.

References:

http://seclists.org/oss-sec/2018/q2/168

An upstream patch:

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

https://marc.info/?l=linux-scsi&m=152933023515279&w=2 (suggested but not approved at the time of this writing)

— Red Hat

Affected Software

38 affected componentsFixes available
Linux Linux kernel>=3.18<=4.16
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Debian Debian Linux=8.0
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1
ubuntu/linux<3.13.0-157.207
3.13.0-157.207
ubuntu/linux-aws<4.4.0-1024.25
4.4.0-1024.25
ubuntu/linux-lts-xenial<4.4.0-130.156~14.04.1
4.4.0-130.156~14.04.1
ubuntu/linux<4.4.0-130.156
4.4.0-130.156
ubuntu/linux-aws<4.4.0-1062.71
4.4.0-1062.71
ubuntu/linux-azure<4.15.0-1022.22~16.04.1
4.15.0-1022.22~16.04.1
ubuntu/linux-gcp<4.15.0-1018.19~16.04.2
4.15.0-1018.19~16.04.2
ubuntu/linux-hwe<4.15.0-33.36~16.04.1
4.15.0-33.36~16.04.1
ubuntu/linux-kvm<4.4.0-1029.34
4.4.0-1029.34
ubuntu/linux-raspi2<4.4.0-1092.100
4.4.0-1092.100
ubuntu/linux-snapdragon<4.4.0-1095.100
4.4.0-1095.100
ubuntu/linux-fips<4.4.0-1008.10
4.4.0-1008.10
ubuntu/linux<4.15.0-33.36
4.15.0-33.36
ubuntu/linux-aws<4.15.0-1020.20
4.15.0-1020.20
ubuntu/linux-azure<4.15.0-1022.23
4.15.0-1022.23
ubuntu/linux-gcp<4.15.0-1018.19
4.15.0-1018.19
ubuntu/linux-kvm<4.15.0-1020.20
4.15.0-1020.20
ubuntu/linux-oem<4.15.0-1017.20
4.15.0-1017.20
ubuntu/linux-raspi2<4.15.0-1021.23
4.15.0-1021.23
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.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Upgrade

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

    Fixed in 3.13.0-157.207
  3. Upgrade

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

    Fixed in 4.4.0-1024.25
  4. Upgrade

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

    Fixed in 4.4.0-130.156~14.04.1
  5. Upgrade

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

    Fixed in 4.4.0-130.156
  6. Upgrade

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

    Fixed in 4.4.0-1062.71
  7. Upgrade

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

    Fixed in 4.15.0-1022.22~16.04.1
  8. Upgrade

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

    Fixed in 4.15.0-1018.19~16.04.2
  9. Upgrade

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

    Fixed in 4.15.0-33.36~16.04.1
  10. Upgrade

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

    Fixed in 4.4.0-1029.34
  11. Upgrade

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

    Fixed in 4.4.0-1092.100
  12. Upgrade

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

    Fixed in 4.4.0-1095.100
  13. Upgrade

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

    Fixed in 4.4.0-1008.10
  14. Upgrade

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

    Fixed in 4.15.0-33.36
  15. Upgrade

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

    Fixed in 4.15.0-1020.20
  16. Upgrade

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

    Fixed in 4.15.0-1022.23
  17. Upgrade

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

    Fixed in 4.15.0-1018.19
  18. Upgrade

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

    Fixed in 4.15.0-1020.20
  19. Upgrade

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

    Fixed in 4.15.0-1017.20
  20. Upgrade

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

    Fixed in 4.15.0-1021.23
  21. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch a45b599ad808c3c982fdcdc12b0b8611c2f92824

Event History

Jun 8, 2018
Data Sourced
via Red Hat·05:12 PM
DescriptionSeverityAffected Software
Jun 26, 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
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Disputed
02:29 PM
Data Sourced
via NVD·02:29 PM
RemedyDescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2018-1000204?

The severity of CVE-2018-1000204 is low.

2

How does CVE-2018-1000204 affect Linux Kernel?

CVE-2018-1000204 affects Linux Kernel versions 3.18 to 4.16.

3

What is the vulnerability in CVE-2018-1000204?

The vulnerability in CVE-2018-1000204 is an incorrect handling of an SG_IO ioctl on /dev/sg0 with dxfer_direction=SG_DXFER_FROM_DEV and an empty 6-byte cmdp, which may lead to copying up to 1000 kernel heap pages to the userspace.

4

Has the vulnerability in CVE-2018-1000204 been fixed?

Yes, the vulnerability has been fixed upstream in the Linux Kernel.

5

Where can I find more information about CVE-2018-1000204?

You can find more information about CVE-2018-1000204 at the following references: [1] [2] [3].

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