From: Vikash Bansal <bvikas@vmware.com>
To: <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <srivatsab@vmware.com>,
<srivatsa@csail.mit.edu>, <amakhalov@vmware.com>,
<srinidhir@vmware.com>, <bvikas@vmware.com>, <anishs@vmware.com>,
<vsirnapalli@vmware.com>, <akaher@vmware.com>, <clm@fb.com>,
<josef@toxicpanda.com>, <dsterba@suse.com>,
<anand.jain@oracle.com>, <linux-btrfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v4.19.y 0/2] btrfs: Fix for CVE-2019-18885
Date: Tue, 9 Jun 2020 12:20:16 +0530 [thread overview]
Message-ID: <20200609065018.26378-1-bvikas@vmware.com> (raw)
CVE Description:
NVD Site Link: https://nvd.nist.gov/vuln/detail?vulnId=CVE-2019-18885
It was discovered that the btrfs file system in the Linux kernel did not
properly validate metadata, leading to a NULL pointer dereference. An
attacker could use this to specially craft a file system image that, when
mounted, could cause a denial of service (system crash).
[PATCH v4.19.y 1/2]:
Backporting of upsream commit 09ba3bc9dd15:
btrfs: merge btrfs_find_device and find_device
[PATCH v4.19.y 2/2]:
Backporting of upstream commit 62fdaa52a3d0:
btrfs: Detect unbalanced tree with empty leaf before crashing
On NVD site link of "commit 09ba3bc9dd150457c506e4661380a6183af651c1"
was given as the fix for this CVE. But the issue was still reproducible.
So had to apply patch "Commit 62fdaa52a3d00a875da771719b6dc537ca79fce1"
to fix the issue.
next reply other threads:[~2020-06-09 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 6:50 Vikash Bansal [this message]
2020-06-09 6:50 ` [PATCH v4.19.y 1/2] btrfs: merge btrfs_find_device and find_device Vikash Bansal
2020-06-09 6:50 ` [PATCH v4.19.y 2/2] btrfs: Detect unbalanced tree with empty leaf before crashing btree operations Vikash Bansal
2020-06-11 11:20 ` [PATCH v4.19.y 0/2] btrfs: Fix for CVE-2019-18885 Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200609065018.26378-1-bvikas@vmware.com \
--to=bvikas@vmware.com \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=anand.jain@oracle.com \
--cc=anishs@vmware.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinidhir@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=stable@vger.kernel.org \
--cc=vsirnapalli@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).