Linux wireless drivers development
 help / color / mirror / Atom feed
From: Heyang Tan <thy15333007817@163.com>
To: chunkeey@googlemail.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] p54: validate firmware record lengths
Date: Sat, 19 Sep 2026 21:26:04 +0800	[thread overview]
Message-ID: <20260919132604.1455-1-thy15333007817@163.com> (raw)

Hi Christian,

A short follow-up with the additional firmware evidence:

- The historical daemonizer archive sample fw-softmac/2.13.1.0.arm is
  available locally. Its published MD5 is
  8ff41cff31c9323330d6170b54735477; local SHA-256 is
  190aa5174c6c08632bf0c452c95509f04ae93705efb7dd88444938fd871d2308.
- Its BR_CODE_DESCR record is 0xb 32-bit words, with rx_start=0x20200 and
  rx_end=0x27c60, so the 0xa minimum descriptor check remains compatible.
- I also generated a private truncated-descriptor fixture for parser-boundary
  testing (SHA-256
  8dc5f14057d46ae0a08f2406d0119991c645365d2dcf8c71c6f5de6fe0f8ad53).

The fixture is not an official linux-firmware image. I have not yet performed
kernel/KASAN execution with it or loaded it on real hardware, so this does not
claim a completed dynamic reproduction or a confirmed CVE.

Regards,
Heyang Tan


             reply	other threads:[~2026-09-19 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 13:26 Heyang Tan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-10  4:16 [PATCH v2] p54: validate firmware record lengths Heyang Tan
2026-09-19 13:36 Heyang Tan
2026-09-19 13:33 Heyang Tan
2026-09-18  8:33 Heyang Tan
2026-09-19 11:01 ` 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=20260919132604.1455-1-thy15333007817@163.com \
    --to=thy15333007817@163.com \
    --cc=chunkeey@googlemail.com \
    --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