From: Namjae Jeon <linkinjeon@kernel.org>
To: Jianzhou Zhao <luckd0g@163.com>
Cc: urezki@gmail.com, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: KASAN: vmalloc-out-of-bounds Write in vfree_atomic
Date: Wed, 11 Mar 2026 19:48:28 +0900 [thread overview]
Message-ID: <CAKYAXd8BPPrEiD+F7LkiFwXo360-VGqADw93ptwCwp5ZVWkGYw@mail.gmail.com> (raw)
In-Reply-To: <57fac928.7af6.19cdc162036.Coremail.luckd0g@163.com>
> ### Proposed Fix:
>
> The solution is natively simple: nullify `sbi->vol_utbl` directly inside `exfat_free_upcase_table()` after freeing it. This safely converts the secondary asynchronous `kvfree` into a no-op.
>
> ```c
> void exfat_free_upcase_table(struct exfat_sb_info *sbi)
> {
> kvfree(sbi->vol_utbl);
> + sbi->vol_utbl = NULL;
> }
> ```
It was already fixed back in early 2025 with commit 1f3d9724e16d
('exfat: fix double free in delayed_free').
prev parent reply other threads:[~2026-03-11 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 8:49 Jianzhou Zhao
2026-03-11 10:48 ` Namjae Jeon [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=CAKYAXd8BPPrEiD+F7LkiFwXo360-VGqADw93ptwCwp5ZVWkGYw@mail.gmail.com \
--to=linkinjeon@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luckd0g@163.com \
--cc=urezki@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