public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Protopopov <a.s.protopopov@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: bpf@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [bug report] bpf: Fix a potential use-after-free of BTF object
Date: Fri, 13 Feb 2026 10:29:57 +0000	[thread overview]
Message-ID: <aY79JehckdNVA2ND@mail.gmail.com> (raw)
In-Reply-To: <aY689z7gHNv8rgVO@stanley.mountain>

On 26/02/13 08:56AM, Dan Carpenter wrote:
> [ Smatch checking is paused while we raise funding. #SadFace
>   https://lore.kernel.org/all/aTaiGSbWZ9DJaGo7@stanley.mountain/ -dan ]
> 
> Hello Anton Protopopov,
> 
> Commit c81e4322acf0 ("bpf: Fix a potential use-after-free of BTF
> object") from Feb 9, 2026 (linux-next), leads to the following Smatch
> static checker warning:
> 
> 	kernel/bpf/verifier.c:25375 add_fd_from_fd_array()
> 	warn: double fget(): 'fd'
> 
> kernel/bpf/verifier.c
>     25360 static int add_fd_from_fd_array(struct bpf_verifier_env *env, int fd)
>     25361 {
>     25362         struct bpf_map *map;
>     25363         struct btf *btf;
>     25364         CLASS(fd, f)(fd);
> 
> This assigns f = fdget(fd);
> 
>     25365         int err;
>     25366 
>     25367         map = __bpf_map_get(f);
>     25368         if (!IS_ERR(map)) {
>     25369                 err = __add_used_map(env, map);
>     25370                 if (err < 0)
>     25371                         return err;
>     25372                 return 0;
>     25373         }
>     25374 
> --> 25375         btf = btf_get_by_fd(fd);
>                                       ^^
> This re-uses the fd.  The reason behind the warning is that the user
> could have changed the fd to point to a different file from the
> start of the function.

True, this could happen. Not sure this is a real problem (if a user
replaced this by a valid BTF, well...)

>     25376         if (!IS_ERR(btf))
>     25377                 return __add_used_btf(env, btf);

The problem with this piece of code is that originally I wanted to
keep naming/appearance in sync, but the corresponding map/btf
functions, historically, behave a bit different...

To keep things working and to address the bug report in this
thread, one fix is required:

-       btf = btf_get_by_fd(fd);
-       if (!IS_ERR(btf))
+       btf = __btf_get_by_fd(f);
+       if (!IS_ERR(btf)) {
+               btf_get(btf);
                return __add_used_btf(env, btf);
+       }

I will send this fix later.

>     25379         verbose(env, "fd %d is not pointing to valid bpf_map or btf\n", fd);
>     25380         return PTR_ERR(map);
>     25381 }
> 
> regards,
> dan carpenter

      reply	other threads:[~2026-02-13 10:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <caa37f28-a2e8-4e0a-a9ce-a365ce805e4b@stanley.mountain>
2026-02-13  5:56 ` [bug report] bpf: Fix a potential use-after-free of BTF object Dan Carpenter
2026-02-13 10:29   ` Anton Protopopov [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=aY79JehckdNVA2ND@mail.gmail.com \
    --to=a.s.protopopov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@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