From: Deepakkumar Karn <dkarn@redhat.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+e07658f51ca22ab65b4e@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com,
Deepakkumar Karn <dkarn@redhat.com>
Subject: [PATCH v2] fs: add NULL check in drop_buffers() to prevent null-ptr-deref
Date: Tue, 9 Dec 2025 00:33:07 +0530 [thread overview]
Message-ID: <20251208190306.518502-2-dkarn@redhat.com> (raw)
drop_buffers() dereferences the buffer_head pointer returned by
folio_buffers() without checking for NULL. This leads to a null pointer
dereference when called from try_to_free_buffers() on a folio with no
buffers attached. This happens when filemap_release_folio() is called on
a folio belonging to a mapping with AS_RELEASE_ALWAYS set but without
release_folio address_space operation defined. In such case,
folio_needs_release() returns true because of AS_RELEASE_ALWAYS flag,
the folio has no private buffer data, causing the try_to_free_buffers()
with a folio that has no buffers.
Adding NULL check for the buffer_head pointer and return false early if
no buffers are attached to the folio.
Reported-by: syzbot+e07658f51ca22ab65b4e@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=e07658f51ca22ab65b4e
Fixes: 6439476311a6 ("fs: Convert drop_buffers() to use a folio")
Signed-off-by: Deepakkumar Karn <dkarn@redhat.com>
---
fs/buffer.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/buffer.c b/fs/buffer.c
index 838c0c571022..fa5de0cdf540 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -2893,6 +2893,10 @@ drop_buffers(struct folio *folio, struct buffer_head **buffers_to_free)
struct buffer_head *head = folio_buffers(folio);
struct buffer_head *bh;
+ /* In cases of folio without buffer_head*/
+ if (!head)
+ return false;
+
bh = head;
do {
if (buffer_busy(bh))
--
2.52.0
next reply other threads:[~2025-12-08 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 19:03 Deepakkumar Karn [this message]
2025-12-08 19:30 ` [PATCH v2] fs: add NULL check in drop_buffers() to prevent null-ptr-deref Darrick J. Wong
2025-12-08 20:13 ` Deepakkumar Karn
2025-12-09 11:18 ` Jan Kara
2025-12-09 16:30 ` Deepak Karn
2025-12-10 9:55 ` Jan Kara
2025-12-10 15:29 ` Deepak Karn
2025-12-10 17:23 ` Jan Kara
2025-12-10 17:50 ` Deepak Karn
2025-12-11 9:15 ` Jan Kara
2025-12-11 12:50 ` Deepak Karn
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=20251208190306.518502-2-dkarn@redhat.com \
--to=dkarn@redhat.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+e07658f51ca22ab65b4e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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