From: John Johansen <john.johansen@canonical.com>
To: lirongqing <lirongqing@baidu.com>,
Georgia Garcia <georgia.garcia@canonical.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
apparmor@lists.ubuntu.com, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apparmor: avoid potential double free when remapping DFA tables
Date: Wed, 28 Oct 2026 15:42:57 -0700 [thread overview]
Message-ID: <9bb8ebd8-d64d-4cb6-89d4-595a3bc4584b@canonical.com> (raw)
In-Reply-To: <20261008031533.2205-1-lirongqing@baidu.com>
On 10/7/26 20:15, lirongqing wrote:
> From: Li RongQing <lirongqing@baidu.com>
>
> When unpacking a DFA, aadfaunpack() stores a table in dfa->tables
> before attempting to remap a 16-bit table to 32-bit.
>
> However, remapdata16todata32() frees the original table when
> allocation of the new table fails. This leaves the corresponding
> dfa->tables entry pointing to freed memory. If the unpacking then
> fails, dfafree() attempts to free the same table again.
>
> Only publish the table to dfa->tables after any required remapping
> has completed successfully, so that dfa->tables never contains a
> pointer to a table that has already been freed.
>
> Fixes: 9208c05f9fdf ("apparmor: add support for 2^24 states to the dfa state machine.")
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
Acked-by: John Johansen <john.johansen@canonical.com>
I have pulled this into the apparmor tree
> ---
> security/apparmor/match.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/security/apparmor/match.c b/security/apparmor/match.c
> index 7713484..ca30a42 100644
> --- a/security/apparmor/match.c
> +++ b/security/apparmor/match.c
> @@ -397,7 +397,6 @@ struct aa_dfa *aa_dfa_unpack(const void *blob, size_t size, int flags)
> /* check for duplicate table entry */
> if (dfa->tables[table->td_id])
> goto fail;
> - dfa->tables[table->td_id] = table;
> data += table_size(table->td_lolen, table->td_flags);
> size -= table_size(table->td_lolen, table->td_flags);
>
> @@ -414,9 +413,9 @@ struct aa_dfa *aa_dfa_unpack(const void *blob, size_t size, int flags)
> if (!table)
> goto fail;
> }
> - dfa->tables[table->td_id] = table;
> break;
> }
> + dfa->tables[table->td_id] = table;
> table = NULL;
> }
> error = verify_table_headers(dfa->tables, flags);
prev parent reply other threads:[~2026-10-28 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 3:15 lirongqing
2026-10-28 22:42 ` John Johansen [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=9bb8ebd8-d64d-4cb6-89d4-595a3bc4584b@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=georgia.garcia@canonical.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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®