From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] apparmor: safely acquire the cached label in aa_file_perm()
Date: Sat, 07 Nov 2026 10:40:23 +0000 [thread overview]
Message-ID: <sashiko-outbox-202819@kernel.org> (raw)
In-Reply-To: <20261107102534.816756-2-bestswngs@gmail.com>
> aa_file_perm() passes an unreferenced RCU snapshot of fctx->label to
> aa_get_newest_label(). Its non-stale branch uses a plain kref_get(). Policy
> replacement can drop the proxy reference after the stale test while
> update_file_ctx() drops the cached reference, so pread64() can increment
> the label's refcount from zero.
>
> Acquire the RCU-published label with kref_get_unless_zero before testing it
> for staleness, keeping the label alive while resolving its replacement.
>
> refcount_t: addition on 0; use-after-free.
> WARNING: lib/refcount.c:25 at refcount_warn_saturate+0x111/0x130, CPU#1: AAVICTIM/5091
> RIP: refcount_warn_saturate (lib/refcount.c:25)
> Call Trace:
> aa_file_perm (security/apparmor/file.c:657)
> common_file_perm (security/apparmor/lsm.c:529)
> security_file_permission (security/security.c:2392)
> rw_verify_area (fs/read_write.c:476)
> vfs_read (fs/read_write.c:566)
> __x64_sys_pread64 (fs/read_write.c:770)
> do_syscall_64 (arch/x86/entry/syscall_64.c:94)
> entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
>
> Fixes: bce4e7e9c45e ("apparmor: reduce rcu_read_lock scope for aa_file_perm mediation")
> Cc: stable@vger.kernel.org
> Reported-by: <co+c85e76ce40a43b9b@bugs.sh>
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261107102534.816756-2-bestswngs@gmail.com?part=1
prev parent reply other threads:[~2026-11-07 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 10:25 [PATCH] apparmor: safely acquire the cached label in aa_file_perm() Weiming Shi
2026-11-07 10:40 ` 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=sashiko-outbox-202819@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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