Re: [PATCH 1/2] kho: expose incoming sub-blob metadata instead of contents
From: Pasha Tatashin
Date: Wed Nov 18 2026 - 11:38:28 EST
> Incoming sub-blob pages are owned by their consumers and have independent
> lifetimes. Some consumers, such as LUO, restore and free their state in
> early_initcall, i.e. before kho_init() (fs_initcall) builds the debugfs
> view:
>
> early_initcall: luo_early_startup()
> -> kho_retrieve_subtree("LUO")
> -> kho_restore_free(luo_ser) /* page is freed */
>
> fs_initcall: kho_init()
> -> kho_in_debugfs_init()
> -> phys_to_virt(luo_ser_phys)
> -> debugfs_create_blob("LUO", ...)
>
> debugfs therefore ends up pointing at a page that was already handed back
> to the page allocator, and reading the file triggers a use-after-free:
>
> # cat /sys/kernel/debug/kho/in/sub_fdts/LUO
> ==================================================================
> BUG: KASAN: use-after-free in _copy_to_user+0x37/0x60
> Read of size 32 at addr ffff88810309c000 by task cat/27436
>
> Call Trace:
> <TASK>
> kasan_report+0xb9/0xf0
> kasan_check_range+0x100/0x1b0
> _copy_to_user+0x37/0x60
> simple_read_from_buffer+0x77/0xd0
> read_file_blob+0x75/0xa0
> vfs_read+0x12d/0x520
> ksys_read+0xc3/0x160
> do_syscall_64+0x97/0x4b0
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
> </TASK>
>
> The buggy address belongs to the physical page:
> page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x1fd
> pfn:0x10309c
> flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff)
> page_type: f0(buddy)
> ==================================================================
>
> The page is already in the buddy allocator (page_type: f0(buddy),
> refcount 0), which confirms it was freed before the debugfs view was
> created.
>
> KHO does not own these pages, so it cannot safely expose their contents at
> all. Drop the in/sub_fdts raw blob nodes and replace them with a
> read-only in/blobs metadata file that lists the name, physical address and
> size of every incoming sub-blob. The FDT itself is reserved by KHO and is
> still exposed as in/fdt.
I suggest we simply remove in/sub_fdts without adding in/blobs. All of
the metadata you are proposing to expose via in/blobs is already present
in in/fdt (and can be parsed from userspace if needed), so I do not
think it warrants adding another kernel debugfs interface. Keeping this
to just removing in/sub_fdts (and updating the doc) also keeps the fix
minimal for -rc.
>
> Fixes: 062dd306d99c ("kho: fix kho_in_debugfs_init() to handle non-FDT blobs")
This UAF has been there since in/sub_fdts was first added, so I think
this should be: Fixes: c609c144b0e8 ("kexec: add KHO parsing support")
--
Pasha