mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH vulns] CVE-2025-68212: Add vulnerable commit information
Date: Sat, 17 Jan 2026 21:18:31 +0530	[thread overview]
Message-ID: <e16c5ddd-6c01-4ff3-acb4-03e47a9a67b7@oracle.com> (raw)
In-Reply-To: <2026011706-antirust-niece-8228@gregkh>

On 17/01/26 21:17, Greg KH wrote:
> On Sat, Jan 17, 2026 at 03:34:26PM +0000, Harshit Mogalapalli wrote:
>> For the CVE fix, the actual broken commit which is more appropriate
>> is 37c4a9590e1e introduces the STATMOUNT_MNT_{U,G}IDMAP cases but only
>> writes sm->mnt_* = start while leaving offp unset.
>>
>> Hence, the broken commit for this CVE is commit: 37c4a9590e1e
>> ("statmount: allow to retrieve idmappings")
>>
>> Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
>> ---
>>   cve/published/2025/CVE-2025-68212.vulnerable | 1 +
>>   1 file changed, 1 insertion(+)
>>   create mode 100644 cve/published/2025/CVE-2025-68212.vulnerable
>>
>> diff --git a/cve/published/2025/CVE-2025-68212.vulnerable b/cve/published/2025/CVE-2025-68212.vulnerable
>> new file mode 100644
>> index 000000000000..602d5fbb79b3
>> --- /dev/null
>> +++ b/cve/published/2025/CVE-2025-68212.vulnerable
>> @@ -0,0 +1 @@
>> +37c4a9590e1efcae7749682239fc22a330d2d325
>> -- 
>> 2.50.1
>>
>>
> 
> Now applied and the records updated, thanks!
> 

Thanks a lot!

Regards,
Harshit

> greg k-h


      reply	other threads:[~2026-01-17 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-17 15:34 Harshit Mogalapalli
2026-01-17 15:47 ` Greg KH
2026-01-17 15:48   ` Harshit Mogalapalli [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=e16c5ddd-6c01-4ff3-acb4-03e47a9a67b7@oracle.com \
    --to=harshit.m.mogalapalli@oracle.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®