From: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>
To: Rolf Eike Beer <eb@emlix.com>
Cc: anton@tuxera.com, gregkh@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, skhan@linuxfoundation.org,
syzbot+213ac8bb98f7f4420840@syzkaller.appspotmail.com,
rkovhaev@gmail.com
Subject: Re: [PATCH] ntfs: Fix validity check for file name attribute
Date: Thu, 29 Jul 2021 19:56:09 +0800 [thread overview]
Message-ID: <e24a9b8c-12c9-eb05-7133-148d16da034b@gmail.com> (raw)
In-Reply-To: <2424055.QlFIqzKPrH@devpool47>
On 29/7/21 4:31 pm, Rolf Eike Beer wrote:
> Hi,
>
> I was just scanning through some older vulnerabilities and came across
> CVE-2018-12929, CVE-2018-12930, and CVE-2018-12931, which are all still open
> according to linuxkernelcves.com (originally reported against 4.15 [1]). I
> looked into the commits in fs/ntfs/ from 4.15 onwards to see if they were just
> missed, but I can't spot anything there. RedHat claims to have them fixed in
> one of their kernels [2].
>
> Which makes me wonder if the issue fixed here is a duplicate of the any of the
> above. Is there a reason I can't find any patches for the original issue in
> tree, like the issue only introduced in a custom patchset that Ubuntu/RedHat
> were using? Is this thing worth it's own CVE if it's no duplicate?
>
> Greetings,
>
> Eike
>
> 1) https://marc.info/?t=152407734400002&r=1&w=2
> 2) https://access.redhat.com/errata/RHSA-2019:0641
>
Hi Eike,
Thanks for digging into this. From a first glance, this bug seems most
similar to CVE-2018-12929.
However, from the logs, the root causes are probably different. The
cause of this bug is specifically in the call to
ntfs_is_extended_system_file [1], but from what I can see this is not
the case for CVE-2018-12929. I don't know enough to comment whether it
needs a CVE, but it has been patched on Linux stable (up to 4.4).
It's worth noting that there's another similar bug that was fixed by
Rustam Kovhaev (+cc) in ntfs_read_locked_inode [2]. This may or may not
have been the issue in CVE-2018-12929.
Link:
https://syzkaller.appspot.com/bug?id=a1a1e379b225812688566745c3e2f7242bffc246
[1]
Link:
https://syzkaller.appspot.com/bug?id=933dab9c03ac47a3d09dd4b0563a0a8fcb35f282
[2]
Best wishes,
Desmond
prev parent reply other threads:[~2021-07-29 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 5:05 [PATCH] ntfs: Fix validity check for file name attribute Desmond Cheong Zhi Xi
2021-06-28 2:45 ` Desmond Cheong Zhi Xi
2021-06-28 9:22 ` Anton Altaparmakov
2021-06-28 9:22 ` Anton Altaparmakov
2021-07-29 8:31 ` Rolf Eike Beer
2021-07-29 11:56 ` Desmond Cheong Zhi Xi [this message]
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=e24a9b8c-12c9-eb05-7133-148d16da034b@gmail.com \
--to=desmondcheongzx@gmail.com \
--cc=anton@tuxera.com \
--cc=eb@emlix.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=rkovhaev@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+213ac8bb98f7f4420840@syzkaller.appspotmail.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