CVE-2018-16862: Infoleak

Published Nov 12, 2018
·
Updated

A security flaw was found in the Linux kernel in a way that the cleancache subsystem clears an inode after the final file truncation (removal). The new file created with the same inode may contain leftover pages from cleancache and the old file data instead of the new one.

Other sources

A security flaw was found in the Linux kernel in a way that the cleancache subsystem clears an inode after the final file truncation (removal). The new file created with the same inode may contain leftover pages from cleancache and so the old file data instead of the new one.

References:

https://seclists.org/oss-sec/2018/q4/169

A suggested patch:

https://lore.kernel.org/patchwork/patch/1011367/

— Red Hat

Affected Software

44 affected componentsFixes available
Linux Linux kernel<=4.14
redhat Enterprise Linux=7.0
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.11-17.2.12-1
ubuntu/linux-aws<4.4.0-1038.41
4.4.0-1038.41
ubuntu/linux-lts-xenial<4.4.0-142.168~14.04.1
4.4.0-142.168~14.04.1
ubuntu/linux-azure<4.15.0-1059.64~14.04.1
4.15.0-1059.64~14.04.1
ubuntu/linux<4.4.0-142.168
4.4.0-142.168
ubuntu/linux-aws<4.4.0-1075.85
4.4.0-1075.85
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-1040.46
4.4.0-1040.46
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-1103.111
4.4.0-1103.111
ubuntu/linux-snapdragon<4.4.0-1107.112
4.4.0-1107.112
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<5.0.0-1014.14~18.04.1
5.0.0-1014.14~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-hwe<5.0.0-23.24~18.04.1
5.0.0-23.24~18.04.1
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*

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.11-1Fixed in 7.2.12-1
  2. Upgrade

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

    Fixed in 4.4.0-1038.41
  3. Upgrade

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

    Fixed in 4.4.0-142.168~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-142.168
  6. Upgrade

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

    Fixed in 4.4.0-1075.85
  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-1040.46
  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-1103.111
  14. Upgrade

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

    Fixed in 4.4.0-1107.112
  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 5.0.0-1014.14~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-hwe to a version that resolves this vulnerability.

    Fixed in 5.0.0-23.24~18.04.1
  22. Upgrade

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

    Fixed in 4.15.0-1042.42
  23. Upgrade

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

    Fixed in 4.15.0-1050.57
  24. Upgrade

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

    Fixed in 4.15.0-1021.23
  25. Upgrade

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

    Fixed in 4.15.0-1043.46
  26. Upgrade

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

    Fixed in 4.15.0-1060.66
  27. Upgrade

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

    Fixed in 4.15.0-2018.18
  28. Upgrade

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

    Fixed in 4.15.0-2006.7

Event History

Nov 12, 2018
Data Sourced
via Red Hat·05:47 PM
DescriptionSeverityAffected Software
Nov 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·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:29 PM
RemedyDescriptionSeverityWeaknessAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2018-16862?

CVE-2018-16862 is considered to be a medium severity vulnerability due to its potential to expose old file data.

2

How do I fix CVE-2018-16862?

To fix CVE-2018-16862, update the Linux kernel to versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.11-1, or 6.12.12-1, or apply patches provided by your OS vendor.

3

What systems are affected by CVE-2018-16862?

CVE-2018-16862 affects the Linux kernel versions up to 4.14 as well as specific versions of Red Hat Enterprise Linux, Ubuntu Linux, and Debian GNU/Linux.

4

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

The potential impacts of CVE-2018-16862 include unintended data exposure where new files might contain data remnants from previously truncated files.

5

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

More information about CVE-2018-16862 can be found in security advisories from your OS vendor and security databases.

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