CVE-2019-19319: Use After Free
An out-of-bounds write flaw was found in the Linux kernel’s Ext4 FileSystem in the way it uses a crafted ext4 image. This flaw allows a local user with physical access to crash the system or potentially escalate their privileges on the system.
Other sources
In the Linux kernel 5.0.21, a setxattr operation, after a mount of a crafted ext4 image, can cause a slab-out-of-bounds write access because of an ext4xattrsetentry use-after-free in fs/ext4/xattr.c when a large oldsize value is used in a memset call.
Reference: https://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19319
— Red Hat
In the Linux kernel before 5.2, a setxattr operation, after a mount of a crafted ext4 image, can cause a slab-out-of-bounds write access because of an ext4xattrsetentry use-after-free in fs/ext4/xattr.c when a large oldsize value is used in a memset call, aka CID-345c0dbf3a30.
— Ubuntu
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/kernel-rtto a version that resolves this vulnerability.Fixed in 0:4.18.0-240.rt7.54.el8 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 0:4.18.0-240.el8 - Upgrade
Upgrade
debian/linuxto 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.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2019-19319?
CVE-2019-19319 is classified as a high severity vulnerability due to the potential for privilege escalation and system crashes.
How do I fix CVE-2019-19319?
To fix CVE-2019-19319, upgrade to kernel version 0:4.18.0-240.rt7.54.el8 or 0:4.18.0-240.el8 for Red Hat, or to the recommended versions for Debian including 5.10.223-1.
What systems are affected by CVE-2019-19319?
CVE-2019-19319 affects specific versions of the Linux kernel, including 5.0.21 and earlier, as well as Red Hat and openSUSE distributions.
Is there a workaround for CVE-2019-19319?
There are no known workarounds for CVE-2019-19319, so updating to a patched version is recommended.
Who is vulnerable to CVE-2019-19319?
Local users with physical access to the system may exploit CVE-2019-19319 to crash the system or escalate privileges.