SCSI target development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandru Hossu <hossu.alexandru@gmail.com>
Cc: security@kernel.org, bvanassche@acm.org, target-devel@vger.kernel.org
Subject: Re: heap buffer overflow in iSCSI CHAP base64 response parsing (iscsi_target_auth.c)
Date: Mon, 18 May 2026 07:28:42 +0200	[thread overview]
Message-ID: <2026051813-path-unsealed-6872@gregkh> (raw)
In-Reply-To: <6a0a00f2.e1ea9722.1dc845.b85e@mx.google.com>

On Sun, May 17, 2026 at 10:54:58AM -0700, Alexandru Hossu wrote:
> Hi,
> 
> Was going through the iSCSI target code looking at what an
> unauthenticated initiator can reach before auth completes. The 2022
> commit that added base64 support to CHAP (1e5733883421, "scsi: target:
> iscsi: Support base64 in CHAP") stood out -- it extends the login path
> with a new decoding branch, so I read through chap_server_compute_hash()
> to see how the new case was handled compared to the existing HEX branch.

As this is public, no need to get security@k.o involved.

Please just send a patch to fix this.

thanks,

greg k-h

      reply	other threads:[~2026-05-18  5:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17 17:54 heap buffer overflow in iSCSI CHAP base64 response parsing (iscsi_target_auth.c) Alexandru Hossu
2026-05-18  5:28 ` Greg KH [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=2026051813-path-unsealed-6872@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bvanassche@acm.org \
    --cc=hossu.alexandru@gmail.com \
    --cc=security@kernel.org \
    --cc=target-devel@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