CVE-2019-19770
published 2019-12-12CVE-2019-19770: In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory…
PriorityP340high8.2CVSS 3.1
AVNACLPRNUINSUCLINAH
EPSS
2.45%
82.5th percentile
In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory in debugfs that was previously created with a call to another debugfs function such as debugfs_create_file). NOTE: Linux kernel developers dispute this issue as not being an issue with debugfs, instead this is an issue with misuse of debugfs within blktrace
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.7.17-1 (bookworm) | linux 5.7.17-1 (bookworm) |
| linux | linux_kernel | <= 4.19.83 | — |
| linux | linux_kernel | >= 0 < 5.7.17-1 | 5.7.17-1 |
| linux | linux_kernel | >= 0 < 5.7.17-1 | 5.7.17-1 |
| linux | linux_kernel | >= 0 < 5.7.17-1 | 5.7.17-1 |
| linux | linux_kernel | >= 0 < 5.7.17-1 | 5.7.17-1 |
| linux | linux_kernel | >= 0 < 4.15.0-129.132 | 4.15.0-129.132 |
CVSS provenance
nvdv3.18.2HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
nvdv2.06.4MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:P
osv8.2HIGH
vendor_debian8.2HIGH
vendor_redhat8.2HIGH
vendor_ubuntu8.2HIGH
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-6xfg-823w-w33f: In the Linux kernel 4
ghsa_unreviewed·2022-05-24
CVE-2019-19770 [MEDIUM] CWE-416 GHSA-6xfg-823w-w33f: In the Linux kernel 4
In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory in debugfs that was previously created with a call to another debugfs function such as debugfs_create_file).
OSV
linux, linux-aws, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-gcp, linux-gcp-4.15, linux-gke-4.15, linux-hwe, linux-kvm, linux-oracle, linux-raspi2, linux-snapdragon vulnerabilities
osv·2021-01-06·CVSS 8.2
CVE-2019-19770 [HIGH] linux, linux-aws, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-gcp, linux-gcp-4.15, linux-gke-4.15, linux-hwe, linux-kvm, linux-oracle, linux-raspi2, linux-snapdragon vulnerabilities
linux, linux-aws, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-gcp, linux-gcp-4.15, linux-gke-4.15, linux-hwe, linux-kvm, linux-oracle, linux-raspi2, linux-snapdragon vulnerabilities
It was discovered that debugfs in the Linux kernel as used by blktrace
contained a use-after-free in some situations. A privileged local attacker
could possibly use this to cause a denial of service (system crash).
(CVE-2019-19770)
It was discovered that a race condition existed in the binder IPC
implementation in the Linux kernel, leading to a use-after-free
vulnerability. A local attacker could use this to cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2020-0423)
Daniele Antonioli, Nils Ole Tippenhauer, and Kasper Rasmussen discovered
that legacy pairing and secur
Kernel
blktrace: fix debugfs use after free
kernel_security·2020-06-19
CVE-2019-19770 blktrace: fix debugfs use after free
blktrace: fix debugfs use after free
On commit 6ac93117ab00 ("blktrace: use existing disk debugfs directory")
merged on v4.12 Omar fixed the original blktrace code for request-based
drivers (multiqueue). This however left in place a possible crash, if you
happen to abuse blktrace while racing to remove / add a device.
We used to use asynchronous removal of the request_queue, and with that
the issue was easier to reproduce. Now that we have reverted to
synchronous removal of the request_queue, the issue is still possible to
reproduce, its however just a bit more difficult.
We essentially run two instances of break-blktrace which add/remove
a loop device, and setup a blktrace and just never tear the blktrace
down. We do this twice in parallel. This is easily reproduced with the
script run
OSV
CVE-2019-19770: In the Linux kernel 4
osv·2019-12-12·CVSS 8.2
CVE-2019-19770 [HIGH] CVE-2019-19770: In the Linux kernel 4
In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory in debugfs that was previously created with a call to another debugfs function such as debugfs_create_file). NOTE: Linux kernel developers dispute this issue as not being an issue with debugfs, instead this is an issue with misuse of debugfs within blktrace
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2021-01-06·CVSS 8.2
CVE-2020-0423 [HIGH] Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
It was discovered that debugfs in the Linux kernel as used by blktrace
contained a use-after-free in some situations. A privileged local attacker
could possibly use this to cause a denial of service (system crash).
(CVE-2019-19770)
It was discovered that a race condition existed in the binder IPC
implementation in the Linux kernel, leading to a use-after-free
vulnerability. A local attacker could use this to cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2020-0423)
Daniele Antonioli, Nils Ole Tippenhauer, and Kasper Rasmussen discovered
that legacy pairing and secure-connections pairing authentication in the
Bluetooth protocol could allow an unauthenti
Red Hat
kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c
vendor_redhat·2019-11-29·CVSS 8.2
CVE-2019-19770 [HIGH] CWE-416 kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c
kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c
In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory in debugfs that was previously created with a call to another debugfs function such as debugfs_create_file). NOTE: Linux kernel developers dispute this issue as not being an issue with debugfs, instead this is an issue with misuse of debugfs within blktrace
A use-after-free flaw was found in the debugfs_remove function in the Linux kernel. The flaw could allow a local attacker with special user (or root) privilege to crash the system at the time of file or directory removal. This vulnerability can lead to a kernel information leak. The highest threat from this vulnerab
Debian
CVE-2019-19770: linux - In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_rem...
vendor_debian·2019·CVSS 8.2
CVE-2019-19770 [HIGH] CVE-2019-19770: linux - In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_rem...
In the Linux kernel 4.19.83, there is a use-after-free (read) in the debugfs_remove function in fs/debugfs/inode.c (which is used to remove a file or directory in debugfs that was previously created with a call to another debugfs function such as debugfs_create_file). NOTE: Linux kernel developers dispute this issue as not being an issue with debugfs, instead this is an issue with misuse of debugfs within blktrace
Scope: local
bookworm: resolved (fixed in 5.7.17-1)
bullseye: resolved (fixed in 5.7.17-1)
forky: resolved (fixed in 5.7.17-1)
sid: resolved (fixed in 5.7.17-1)
trixie: resolved (fixed in 5.7.17-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-19770 kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c
bugzilla·2019-12-23·CVSS 8.2
CVE-2019-19770 [HIGH] CVE-2019-19770 kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c
CVE-2019-19770 kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c
A use-after-free flaw was found in the debugfs_remove function in the Linux kernel. The flaw could allow a local attacker with special user (or root) privilege to crash the system at the time of file or directory removal. This vulnerability can lead to a kernel information leak. The highest threat from this vulnerability is to system availability.
Reference:
https://bugzilla.kernel.org/show_bug.cgi?id=205713
https://lore.kernel.org/linux-block/[email protected]/
Discussion:
Created kernel tracking bugs for this issue:
Affects: fedora-all [bug 1786181]
---
https://lore.kernel.org/linux-fsdevel/[email protected]/T/#mc62cc15324d1da505c6a9c50e3363f4d20537d45
Looks l
Bugzilla
CVE-2019-19770 kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c [fedora-all]
bugzilla·2019-12-23·CVSS 8.2
CVE-2019-19770 [HIGH] CVE-2019-19770 kernel: use-after-free in debugfs_remove in fs/debugfs/inode.c [fedora-all]
CVE-2019-19770 kernel: use-after-free in debugfs_remove in fs/debugfs/inode.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 multiple suppo
http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00035.htmlhttps://bugzilla.kernel.org/show_bug.cgi?id=205713https://lists.debian.org/debian-lts-announce/2020/12/msg00015.htmlhttps://lore.kernel.org/linux-block/20200402000002.7442-1-mcgrof%40kernel.org/https://security.netapp.com/advisory/ntap-20200103-0001/http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00035.htmlhttps://bugzilla.kernel.org/show_bug.cgi?id=205713https://lists.debian.org/debian-lts-announce/2020/12/msg00015.htmlhttps://lore.kernel.org/linux-block/20200402000002.7442-1-mcgrof%40kernel.org/https://security.netapp.com/advisory/ntap-20200103-0001/
2019-12-12
Published