CVE-2019-19037
published 2019-11-21CVE-2019-19037: ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be…
PriorityP421medium5.5CVSS 3.1
AVLACLPRNUIRSUCNINAH
EPSS
1.89%
77.5th percentile
ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.4.8-1 (bookworm) | linux 5.4.8-1 (bookworm) |
| linux | linux_kernel | <= 5.3.12 | — |
| linux | linux_kernel | >= 0 < 5.4.8-1 | 5.4.8-1 |
| linux | linux_kernel | >= 0 < 5.4.8-1 | 5.4.8-1 |
| linux | linux_kernel | >= 0 < 5.4.8-1 | 5.4.8-1 |
| linux | linux_kernel | >= 0 < 5.4.8-1 | 5.4.8-1 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:N/A:P
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-98hp-cmc8-vgp6: ext4_empty_dir in fs/ext4/namei
ghsa_unreviewed·2022-05-24
CVE-2019-19037 [MEDIUM] GHSA-98hp-cmc8-vgp6: ext4_empty_dir in fs/ext4/namei
ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
Kernel
ext4: fix ext4_empty_dir() for directories with holes
kernel_security·2019-12-02·CVSS 5.5
CVE-2019-19037 [MEDIUM] ext4: fix ext4_empty_dir() for directories with holes
ext4: fix ext4_empty_dir() for directories with holes
Function ext4_empty_dir() doesn't correctly handle directories with
holes and crashes on bh->b_data dereference when bh is NULL. Reorganize
the loop to use 'offset' variable all the times instead of comparing
pointers to current direntry with bh->b_data pointer. Also add more
strict checking of '.' and '..' directory entries to avoid entering loop
in possibly invalid state on corrupted filesystems.
References: CVE-2019-19037
CC: [email protected]
Fixes: 4e19d6b65fb4 ("ext4: allow directory holes")
Signed-off-by: Jan Kara
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Theodore Ts'o
OSV
CVE-2019-19037: ext4_empty_dir in fs/ext4/namei
osv·2019-11-21·CVSS 5.5
CVE-2019-19037 [MEDIUM] CVE-2019-19037: ext4_empty_dir in fs/ext4/namei
ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
Red Hat
kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c
vendor_redhat·2019-11-18·CVSS 5.5
CVE-2019-19037 [MEDIUM] CWE-476 kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c
kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c
ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
A NULL pointer dereference 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.
Statement: This issue is rated as having Low impact because of the preconditions needed to trigger the issue (physical access or user interaction to mount the crafted filesystem image).
Mitigation: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deploymen
Debian
CVE-2019-19037: linux - ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NU...
vendor_debian·2019·CVSS 5.5
CVE-2019-19037 [MEDIUM] CVE-2019-19037: linux - ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NU...
ext4_empty_dir in fs/ext4/namei.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
Scope: local
bookworm: resolved (fixed in 5.4.8-1)
bullseye: resolved (fixed in 5.4.8-1)
forky: resolved (fixed in 5.4.8-1)
sid: resolved (fixed in 5.4.8-1)
trixie: resolved (fixed in 5.4.8-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-19037 kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c [fedora-all]
bugzilla·2019-11-21·CVSS 5.5
CVE-2019-19037 [MEDIUM] CVE-2019-19037 kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c [fedora-all]
CVE-2019-19037 kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multipl
Bugzilla
CVE-2019-19037 kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c
bugzilla·2019-11-21·CVSS 5.5
CVE-2019-19037 [MEDIUM] CVE-2019-19037 kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c
CVE-2019-19037 kernel: null-pointer dereference in ext4_empty_dir in fs/ext4/namei.c
A vulnerability was found in ext4_empty_dir in fs/ext4/namei.c in the Linux kernel allows a NULL pointer dereference because ext4_read_dirblock(inode,0,DIRENT_HTREE) can be zero.
Reference:
https://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19037
Discussion:
Created kernel tracking bugs for this issue:
Affects: fedora-all [bug 1775183]
---
This is fixed for Fedora with the 5.4.7 stable kernel updates.
---
Mitigation:
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
---
Statement:
This issue is rated as having
https://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19037https://lists.debian.org/debian-lts-announce/2020/03/msg00001.htmlhttps://security.netapp.com/advisory/ntap-20191205-0001/https://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19037https://lists.debian.org/debian-lts-announce/2020/03/msg00001.htmlhttps://security.netapp.com/advisory/ntap-20191205-0001/
2019-11-21
Published