linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "slava@dubeyko.com" <slava@dubeyko.com>,
	"dan.carpenter@linaro.org" <dan.carpenter@linaro.org>
Cc: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
	"frank.li@vivo.com" <frank.li@vivo.com>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>
Subject: Re:  [PATCH] hfs: fix potential use after free in hfs_correct_next_unused_CNID()
Date: Fri, 3 Oct 2025 21:47:26 +0000	[thread overview]
Message-ID: <8894cbfbf360890f5f781035a345b0d70d0d3d3c.camel@ibm.com> (raw)
In-Reply-To: <aN-Xw8KnbSnuIcLk@stanley.mountain>

On Fri, 2025-10-03 at 12:30 +0300, Dan Carpenter wrote:
> This code calls hfs_bnode_put(node) which drops the refcount and then
> dreferences "node" on the next line.  It's only safe to use "node"
> when we're holding a reference so flip these two lines around.
> 
> Fixes: a06ec283e125 ("hfs: add logic of correcting a next unused CNID")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
>  fs/hfs/catalog.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/hfs/catalog.c b/fs/hfs/catalog.c
> index caebabb6642f..b80ba40e3877 100644
> --- a/fs/hfs/catalog.c
> +++ b/fs/hfs/catalog.c
> @@ -322,9 +322,9 @@ int hfs_correct_next_unused_CNID(struct super_block *sb, u32 cnid)
>  			}
>  		}
>  
> +		node_id = node->prev;
>  		hfs_bnode_put(node);
>  
> -		node_id = node->prev;
>  	} while (node_id >= leaf_head);
>  
>  	return -ENOENT;

Yeah, makes sense. Good catch. :) I missed this. Thanks a lot for the fix.

Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>

Thanks,
Slava.

      reply	other threads:[~2025-10-03 21:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03  9:30 [PATCH] hfs: fix potential use after free in hfs_correct_next_unused_CNID() Dan Carpenter
2025-10-03 21:47 ` Viacheslav Dubeyko [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=8894cbfbf360890f5f781035a345b0d70d0d3d3c.camel@ibm.com \
    --to=slava.dubeyko@ibm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slava@dubeyko.com \
    /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;
as well as URLs for NNTP newsgroup(s).