CVE-2019-11487: Use After Free

Published Apr 22, 2019
·
Updated

A flaw was found in the Linux kernel's implementation of the FUSE filesystem, where it allows a page reference counter overflow. If a page reference counter overflows into a negative value, it can be placed back into the "free" list for reuse by other applications. This flaw allows a local attacker who can manipulate memory page reference counters to cause memory corruption and possible privilege escalation by triggering a use-after-free condition. The current attack requires the system to have approximately 140 GB of RAM for this attack to be performed. It may be possible that the attack can occur with fewer memory requirements.

Other sources

A flaw was found in the linux kernel's implementation of the FUSE filesystem, which allows for a page reference counter overflow. If a page reference counter overflows into a negative value it can be put back into the "free" list for re-use by other applications.

A local attacker who is able to manipulate memory page reference counters can abuse this situation to allow for memory corruption and possibly privilege escalation by triggering a Use After Free condition.

The current attack requires the system to have approximately 140 GiB of RAM for this attack to be carried out. It may be possible that the attack can be carried out with lesser memory requirements.

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

Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6b3a707736301c2128ca85ce85fb13f60b5e350a

Red Hat

Linux Kernel is vulnerable to a denial of service, caused by a page->refcount overflow. A local attacker could exploit this vulnerability using FUSE with ~140GiB RAM usage to cause a denial of service.

IBM

The Linux kernel before 5.1-rc5 allows page->refcount reference count overflow, with resultant use-after-free issues, if about 140 GiB of RAM exists. This is related to fs/fuse/dev.c, fs/pipe.c, fs/splice.c, include/linux/mm.h, include/linux/pipefsi.h, kernel/trace/trace.c, mm/gup.c, and mm/hugetlb.c. It can occur with FUSE requests.

Affected Software

24 affected componentsFixes available
redhat/kernel<0:2.6.32-754.35.1.el6
0:2.6.32-754.35.1.el6
redhat/kernel-rt<0:3.10.0-1062.18.1.rt56.1044.el7
0:3.10.0-1062.18.1.rt56.1044.el7
redhat/kernel-alt<0:4.14.0-115.17.1.el7a
0:4.14.0-115.17.1.el7a
redhat/kernel<0:3.10.0-1062.18.1.el7
0:3.10.0-1062.18.1.el7
redhat/kernel<0:3.10.0-693.71.2.el7
0:3.10.0-693.71.2.el7
redhat/kernel<0:3.10.0-957.56.1.el7
0:3.10.0-957.56.1.el7
redhat/kernel-rt<0:4.18.0-80.11.1.rt9.156.el8_0
0:4.18.0-80.11.1.rt9.156.el8_0
redhat/kernel<0:4.18.0-80.11.1.el8_0
0:4.18.0-80.11.1.el8_0
redhat/kernel-rt<1:3.10.0-693.71.2.rt56.670.el6
1:3.10.0-693.71.2.rt56.670.el6
IBM Data Risk Manager<=2.0.6
Linux Linux kernel<4.4.216
Linux Linux kernel>=4.5<4.9.181
Linux Linux kernel>=4.10<4.14.116
Linux Linux kernel>=4.15<4.19.39
Linux Linux kernel>=4.20<5.0.12
Linux Linux kernel=5.1-rc1
Linux Linux kernel=5.1-rc2
Linux Linux kernel=5.1-rc3
Linux Linux kernel=5.1-rc4
Debian Debian Linux=8.0
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
debian/linux
5.10.223-15.10.257-16.1.170-36.1.174-16.12.86-16.12.90-27.0.10-17.0.12-2

Remediation

Information

Preventing loading of the 'fuse' kernel module will prevent attackers from using this exploit against the system; howeve the functionality of being able to access the filesystems that would be allowed by fuse would no longer be allowed . See “How do I blacklist a kernel module to prevent it from loading automatically?" ( https://access.redhat.com/solutions/41278) for instructions on how to disable the 'fuse' kernel module from autoloading. This mitigation may not be suitable if access to the functionality provided by fuse is required.

Event History

Apr 22, 2019
CVE Published
12:00 AM
Apr 23, 2019
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Apr 25, 2019
Data Sourced
via Red Hat·12:20 PM
DescriptionSeverityAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·11:14 PM
Description
May 23, 2026
Data Sourced
via Ubuntu·09:31 AM
RemedyDescriptionSeverityAffected Software
Jun 13, 2026
Data Sourced
via Debian·09:53 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2019-11487?

CVE-2019-11487 is classified as a high severity vulnerability due to the potential for local attackers to exploit it.

2

How do I fix CVE-2019-11487?

To mitigate CVE-2019-11487, upgrade to the fixed kernel versions specified by your Linux distribution.

3

What systems are affected by CVE-2019-11487?

CVE-2019-11487 affects various Linux kernel versions including those used in Red Hat, Ubuntu, and Debian operating systems.

4

Can CVE-2019-11487 be exploited remotely?

No, CVE-2019-11487 requires local access to the system to be exploited.

5

Is there a patch available for CVE-2019-11487?

Yes, multiple patches are available in the updated kernel versions from affected distributions.

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