]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
mm/slub: avoid accessing metadata when pointer is invalid in object_err()
authorLi Qiong <liqiong@nfschina.com>
Sat, 6 Sep 2025 21:25:30 +0000 (17:25 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 9 Sep 2025 16:58:22 +0000 (18:58 +0200)
[ Upstream commit b4efccec8d06ceb10a7d34d7b1c449c569d53770 ]

object_err() reports details of an object for further debugging, such as
the freelist pointer, redzone, etc. However, if the pointer is invalid,
attempting to access object metadata can lead to a crash since it does
not point to a valid object.

One known path to the crash is when alloc_consistency_checks()
determines the pointer to the allocated object is invalid because of a
freelist corruption, and calls object_err() to report it. The debug code
should report and handle the corruption gracefully and not crash in the
process.

In case the pointer is NULL or check_valid_pointer() returns false for
the pointer, only print the pointer value and skip accessing metadata.

Fixes: 81819f0fc828 ("SLUB core")
Cc: <stable@vger.kernel.org>
Signed-off-by: Li Qiong <liqiong@nfschina.com>
Reviewed-by: Harry Yoo <harry.yoo@oracle.com>
Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
mm/slub.c

index 7e1af40a65f06b9def4dbc942696bfdccbdfd54b..7fbba36f7aac527b2ae9bcda4d1f7b07434015d1 100644 (file)
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -1113,7 +1113,12 @@ static void object_err(struct kmem_cache *s, struct slab *slab,
                return;
 
        slab_bug(s, reason);
-       print_trailer(s, slab, object);
+       if (!object || !check_valid_pointer(s, slab, object)) {
+               print_slab_info(slab);
+               pr_err("Invalid pointer 0x%p\n", object);
+       } else {
+               print_trailer(s, slab, object);
+       }
        add_taint(TAINT_BAD_PAGE, LOCKDEP_NOW_UNRELIABLE);
 
        WARN_ON(1);