mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Cen Zhang <zzzccc427@gmail.com>
Cc: ivan.orlov0322@gmail.com, perex@perex.cz, tiwai@suse.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	baijiaju1990@gmail.com, jjzuming@gmail.com
Subject: Re: [PATCH] ALSA: pcmtest: Pin the module while pattern files are open
Date: Mon, 19 Oct 2026 16:22:05 +0200	[thread overview]
Message-ID: <875wyxahyq.wl-tiwai@suse.de> (raw)
In-Reply-To: <pm-pmb-1ce354e709dbab28e563-v2-6b2ea0aa16ec39442f6d@gmail.com>

On Mon, 19 Oct 2026 11:04:42 +0200,
Cen Zhang wrote:
> 
> The fill_pattern_fops table must remain alive until the final release
> of each pattern debugfs file. It has no .owner, so the fops_get() call
> in full_proxy_open_regular() does not take a PCMTest module reference.
> 
> With snd-pcmtest loaded as a module, a user with permission to open a
> fill_patternN file and unload the module can retain the descriptor
> across normal unload, provided no PCM file or other module reference
> prevents it. The following ordering is possible:
> 
>   Pattern file user                   Module unload
>   -----------------                   -------------
>   open(fill_patternN)
>     full_proxy_open_regular()
>       fops_get(fill_pattern_fops)
>         owner == NULL: no module pin
>   keep the descriptor open
>                                       mod_exit()
>                                         clear_debug_files()
>                                           debugfs_remove_recursive()
>                                           drain active operations
>                                       return from mod_exit()
>                                       free_module()
>                                         free the module image
>   close(fd)
>     full_proxy_release()
>       read real_fops->release -> UAF
>       fops_put(real_fops)
>         read real_fops->owner
>       access freed module memory
> 
> Even though the table has no release callback, reading those fields
> is a use-after-free and can fault. The retained dentry keeps the
> proxy's bookkeeping alive, but does not retain the module storage.
> 
> Set .owner to THIS_MODULE so the existing fops_get()/fops_put() pair
> pins PCMTest until final release has finished accessing the table.
> Normal module unload is then blocked while any pattern file is open.
> 
> Fixes: 315a3d57c64c ("ALSA: Implement the new Virtual PCM Test Driver")
> Signed-off-by: Cen Zhang <zzzccc427@gmail.com>
> Assisted-by: LLM

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-10-19 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  9:04 Cen Zhang
2026-10-19 14:22 ` Takashi Iwai [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=875wyxahyq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=baijiaju1990@gmail.com \
    --cc=ivan.orlov0322@gmail.com \
    --cc=jjzuming@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=zzzccc427@gmail.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

all inboxes | Powered by JetHome®