mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heyang Tan <thy15333007817@163.com>
To: linux-wireless@vger.kernel.org
Cc: chunkeey@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] p54: validate firmware record lengths
Date: Wed, 14 Oct 2026 11:32:04 +0800	[thread overview]
Message-ID: <20261014033204.1985-1-thy15333007817@163.com> (raw)

Hi Christian,

Thank you very much for reviewing the v3 patch and for providing your
Acked-by and Tested-by tags. I sincerely appreciate your careful testing
and guidance throughout the revisions.

May I also ask for your technical opinion on the security classification
of this issue? The malformed firmware records could cause out-of-bounds
reads in the kernel firmware parser, but I understand that the practical
security impact may depend on how the firmware can be supplied or replaced.

In your opinion, would this issue be appropriate for consideration by the
Linux kernel CVE team after the fix is merged and included in a released
stable kernel, or would it be more appropriate to regard it as a regular
firmware-parser robustness fix?

I understand that CVE assignment is handled by the Linux kernel CVE team,
and I am not asking you to make that decision or take any action on my
behalf. I would simply be very grateful for your technical advice on
whether contacting cve@kernel.org after the fix is released would be
reasonable.

Thank you again for your time, testing, and helpful review.

Best regards,
Heyang Tan
School of Software
Taiyuan University of Technology


             reply	other threads:[~2026-10-14  3:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  3:32 Heyang Tan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-10  3:37 Heyang Tan
2026-10-10 18:06 ` Christian Lamparter

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=20261014033204.1985-1-thy15333007817@163.com \
    --to=thy15333007817@163.com \
    --cc=chunkeey@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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®