CVE-2018-18281: High severity Linux Linux kernel vulnerability

Published Oct 30, 2018
·
Updated

Last updated 4 July 2026

Other sources

Since Linux kernel version 3.2, the mremap() syscall performs TLB flushes after dropping pagetable locks. If a syscall such as ftruncate() removes entries from the pagetables of a task that is in the middle of mremap(), a stale TLB entry can remain for a short time that permits access to a physical page after it has been released back to the page allocator and reused.

References:

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

https://bugs.chromium.org/p/project-zero/issues/detail?id=1695

An upstream patch:

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

— Red Hat

Since Linux kernel version 3.2, the mremap() syscall performs TLB flushes after dropping pagetable locks. If a syscall such as ftruncate() removes entries from the pagetables of a task that is in the middle of mremap(), a stale TLB entry can remain for a short time that permits access to a physical page after it has been released back to the page allocator and reused. This is fixed in the following kernel versions: 4.9.135, 4.14.78, 4.18.16, 4.19.

— Launchpad

Affected Software

12 affected componentsFixes available
Linux Linux kernel>=3.2<4.9.135
Linux Linux kernel>=4.9.136<4.14.78
Linux Linux kernel>=4.14.79<4.18.16
Linux Linux kernel>=4.18.17<4.19
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=18.10
Debian Debian Linux=8.0
Google Android
debian/linux
6.1.176-16.1.187-16.12.107-16.12.111-17.2.9-17.2.10-1

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.187-1Fixed in 6.12.107-1Fixed in 6.12.111-1Fixed in 7.2.9-1Fixed in 7.2.10-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.9.135
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.14.78
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.18.16
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.19

Event History

Oct 30, 2018
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Data Sourced
via NVD·06:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 1, 2018
Data Sourced
via Red Hat·12:54 PM
DescriptionSeverityAffected Software
Jan 7, 2019
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·10:56 PM
Description
Jul 4, 2026
Data Sourced
via Ubuntu·11:29 AM
RemedyDescriptionSeverityAffected Software
Oct 13, 2026
Data Sourced
via Debian·12:56 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2018-18281?

CVE-2018-18281 has been classified as high severity due to the potential for stale TLB entries leading to memory corruption.

2

How do I fix CVE-2018-18281?

To resolve CVE-2018-18281, update the Linux kernel to version 5.10.223-1 or later.

3

Which Linux kernel versions are affected by CVE-2018-18281?

CVE-2018-18281 affects Linux kernel versions from 3.2 up to 4.19.

4

Is CVE-2018-18281 present in Ubuntu releases?

Yes, CVE-2018-18281 is present in several Ubuntu releases including 12.04, 14.04, 16.04, 18.04, and 18.10.

5

Does CVE-2018-18281 affect Android devices?

Yes, CVE-2018-18281 affects Android devices running on vulnerable versions of 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