From: dhruvg1529@gmail.com
To: kernelci@lists.linux.dev
Subject: Security Concern
Date: Fri, 19 Sep 2025 07:53:31 -0700 (PDT) [thread overview]
Message-ID: <68cd6e6b.630a0220.419fa.4f15@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
Hello,
I'm Dhruv, a cybersecurity researcher and bug hunter. I've discovered a significant bug on your website. Could you confirm if you have a bug bounty program?
I'd like to responsibly disclose the details in exchange for a bounty to prevent any potential misuse.
Thanks & Regards,
Dhruv
reply other threads:[~2025-09-19 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68cd6e6b.630a0220.419fa.4f15@mx.google.com \
--to=dhruvg1529@gmail.com \
--cc=kernelci@lists.linux.dev \
/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