From: Greg KH <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org, vegard.nossum@oracle.com
Subject: Re: [PATCH] Add vulnerable commits for few CVEs
Date: Sat, 10 May 2025 18:47:21 +0200 [thread overview]
Message-ID: <2025051059-knapsack-imbecile-9bb0@gregkh> (raw)
In-Reply-To: <20250510161043.473006-1-harshit.m.mogalapalli@oracle.com>
On Sat, May 10, 2025 at 09:10:43AM -0700, Harshit Mogalapalli wrote:
> CVE-2025-21872: Re-mapping the entire mokvar_table is the problem and
> the re-mapping is first done in this Fixes: 58c909022a5a ("efi: Support
> for MOK variable config table"), so this is the broken commit
>
> CVE-2025-21833: The fix moves dev_pasid dereference inside
> WARN_ON_ONCE() as there is a possibility of dev_pasid being NULL, this
> dereference is first introduced while adding debugfs support per file in
> Fixes: d87731f60931 ("iommu/vt-d: debugfs: Create/remove debugfs file
> per {device, pasid}")
>
> CVE-2025-21832E: The problem is that iov_iter_revert() is done before a
I don't think CVE entries have "E" on the end of them :)
I'll edit this when I apply it in a few minutes, thanks!
greg k-h
next prev parent reply other threads:[~2025-05-10 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 16:10 [PATCH] Add vulnerable commits for few CVEs Harshit Mogalapalli
2025-05-10 16:47 ` Greg KH [this message]
2025-05-10 16:56 ` Harshit Mogalapalli
-- strict thread matches above, loose matches on Subject: below --
2025-03-10 6:23 Harshit Mogalapalli
2025-03-10 7:37 ` Greg KH
2025-03-10 8:48 ` Harshit Mogalapalli
2025-01-20 17:10 Harshit Mogalapalli
2025-01-21 10:56 ` 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=2025051059-knapsack-imbecile-9bb0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.