DMA Engine development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: dmaengine@vger.kernel.org, Frank.Li@kernel.org, vkoul@kernel.org
Subject: Re: [PATCH] dmaengine: at_hdmac: fix memory leak in atc_prep_slave_sg
Date: Thu, 23 Jul 2026 05:16:12 +0000	[thread overview]
Message-ID: <20260723051612.E01571F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260723050402.272606-1-rosenp@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] NULL Pointer Dereference in atdma_desc_free during descriptor preparation error paths.
--

--- Patch [1]: [PATCH] dmaengine: at_hdmac: fix memory leak in atc_prep_slave_sg ---
commit 59e07e1618be88a67e6deaa08218ec2ae653a007
Author: Rosen Penev <rosenp@gmail.com>

dmaengine: at_hdmac: fix memory leak in atc_prep_slave_sg

This commit fixes a memory leak in the default switch case of the slave
scatter-gather preparation function. It adds a missing free for the
allocated descriptor before returning on an invalid direction.

> diff --git a/drivers/dma/at_hdmac.c b/drivers/dma/at_hdmac.c
> index e5b30a57c477a..7763a94d3f998 100644
> --- a/drivers/dma/at_hdmac.c
> +++ b/drivers/dma/at_hdmac.c
> @@ -1381,6 +1381,7 @@ atc_prep_slave_sg(struct dma_chan *chan, struct scatterlist *sgl,
>  		}
>  		break;
>  	default:
> +		kfree(desc);
>  		return NULL;
>  	}

[Severity: High]
This is a pre-existing issue, but while reviewing this error handling I noticed
a potential NULL pointer dereference in the other error paths of this function.

If dma_pool_alloc() fails or an SG list has a zero-length entry, the code
jumps to the error path:

err_desc_get:
        dev_err(chan2dev(chan), "not enough descriptors available\n");
err:
        atdma_desc_free(&desc->vd);
        return NULL;

Inside atdma_desc_free(), it immediately evaluates the device from the channel:

static void atdma_desc_free(struct virt_dma_desc *vd)
{
        struct at_dma *atdma = to_at_dma(vd->tx.chan->device);
        ...
}

Since desc was just allocated with kzalloc_flex() which zeroes memory, and
vd->tx.chan is not initialized until vchan_tx_prep() is called at the end of
atc_prep_slave_sg(), won't vd->tx.chan still be NULL during this cleanup?

Does this code trigger a panic when attempting to dereference the NULL channel
pointer?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260723050402.272606-1-rosenp@gmail.com?part=1

      reply	other threads:[~2026-07-23  5:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  5:04 [PATCH] dmaengine: at_hdmac: fix memory leak in atc_prep_slave_sg Rosen Penev
2026-07-23  5:16 ` sashiko-bot [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=20260723051612.E01571F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=rosenp@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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