All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	b43-dev@lists.infradead.org,
	"David S. Miller" <davem@davemloft.net>,
	linux-wireless@vger.kernel.org
Subject: [PATCH 0/3] wifi: NULL terminate some user strings
Date: Thu, 1 Oct 2026 10:37:35 +0300	[thread overview]
Message-ID: <cover.1790839793.git.error27@gmail.com> (raw)

These strings come from the user and they need to be NUL terminated.

Dan Carpenter (3):
  wifi: b43: don't pass unterminated string to sscanf()
  wifi: b43legacy: debugfs: NUL terminate string in debugfs
  wifi: carl9170: NUL terminate string in debugfs

 drivers/net/wireless/ath/carl9170/debug.c         | 5 +++--
 drivers/net/wireless/broadcom/b43/debugfs.c       | 2 +-
 drivers/net/wireless/broadcom/b43legacy/debugfs.c | 2 +-
 3 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.53.0


WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <error27@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	b43-dev@lists.infradead.org,
	"David S. Miller" <davem@davemloft.net>,
	linux-wireless@vger.kernel.org
Subject: [PATCH 0/3] wifi: NULL terminate some user strings
Date: Thu, 1 Oct 2026 10:37:35 +0300	[thread overview]
Message-ID: <cover.1790839793.git.error27@gmail.com> (raw)

These strings come from the user and they need to be NUL terminated.

Dan Carpenter (3):
  wifi: b43: don't pass unterminated string to sscanf()
  wifi: b43legacy: debugfs: NUL terminate string in debugfs
  wifi: carl9170: NUL terminate string in debugfs

 drivers/net/wireless/ath/carl9170/debug.c         | 5 +++--
 drivers/net/wireless/broadcom/b43/debugfs.c       | 2 +-
 drivers/net/wireless/broadcom/b43legacy/debugfs.c | 2 +-
 3 files changed, 5 insertions(+), 4 deletions(-)

-- 
2.53.0


_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev

             reply	other threads:[~2026-10-01  7:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  7:37 Dan Carpenter [this message]
2026-10-01  7:37 ` [PATCH 0/3] wifi: NULL terminate some user strings Dan Carpenter
2026-10-01  7:37 ` [PATCH 1/3] wifi: b43: don't pass unterminated string to sscanf() Dan Carpenter
2026-10-01  7:37   ` Dan Carpenter
2026-10-01  7:37 ` [PATCH 2/3] wifi: b43legacy: debugfs: NUL terminate string in debugfs Dan Carpenter
2026-10-01  7:37   ` Dan Carpenter
2026-10-01  7:37 ` [PATCH 3/3] wifi: carl9170: " Dan Carpenter
2026-10-01 17:58   ` Christian Lamparter
2026-10-01 18:31     ` Dan Carpenter
2026-10-03 22:49   ` Jeff Johnson

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=cover.1790839793.git.error27@gmail.com \
    --to=error27@gmail.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=chunkeey@googlemail.com \
    --cc=davem@davemloft.net \
    --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 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.