From: Rolf Eike Beer <eb@emlix.com>
To: desmondcheongzx@gmail.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
Subject: Re: [PATCH] ntfs: Fix validity check for file name attribute
Date: Thu, 29 Jul 2021 10:31:45 +0200 [thread overview]
Message-ID: <2424055.QlFIqzKPrH@devpool47> (raw)
In-Reply-To: <20210614050540.289494-1-desmondcheongzx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
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
--
Rolf Eike Beer, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax +49 551 30664-11
Gothaer Platz 3, 37083 Göttingen, Germany
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
Geschäftsführung: Heike Jordan, Dr. Uwe Kracke – Ust-IdNr.: DE 205 198 055
emlix - smart embedded open source
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 313 bytes --]
next prev parent reply other threads:[~2021-07-29 8:40 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 [this message]
2021-07-29 11:56 ` Desmond Cheong Zhi Xi
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=2424055.QlFIqzKPrH@devpool47 \
--to=eb@emlix.com \
--cc=anton@tuxera.com \
--cc=desmondcheongzx@gmail.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=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