kfence_free(9)

💖 kfence_free(9) 💖

okay so bestie, welcome to the kfence_free page from the Kernel API Manual — grab a lil snack, this one's short and sweet 🍓

---

✨ NAME ✨

kfence_free — the "hey, maybe this is a KFENCE object?" release move, aka trying to hand an arbitrary heap object back to the KFENCE pool 🎀

---

🌸 SYNOPSIS 🌸

bool kfence_free (void *addr );

---

🦋 ARGUMENTS 🦋

• addr — the object you're trying to free, bestie. that's it. that's the whole vibe 💅

---

⭐ RETURN ⭐

• false — the object does not belong to the KFENCE pool, so it got ignored 🙈
• true — slay, the object was released to the KFENCE pool 👑

---

💜 DESCRIPTION 💜

Release a KFENCE object and mark it as freed ✨ May be called on any object — yes, literally any object, even the non-KFENCE ones — because it makes integrating the hooks into the allocator's free codepath way simpler 🫶

But listen: the allocator must check the return value to figure out whether it was a KFENCE object or not. no skipping the vibe check, fr fr 🔥

---

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/kfence.h
• is_kfence_address(9)
• kfence_alloc_pool_and_metadata(9)
• kfence_init(9)
• kfence_shutdown_cache(9)
• kfence_alloc(9)
• kfence_ksize(9)
• kfence_object_start(9)
• __kfence_free(9)
• kfence_handle_page_fault(9)
• __kfence_obj_info(9)

---

and that's the whole page, icon periodt 💅✨ this lil gem lives over in ./include/linux and it's dated October 2026 — go read the whole kfence family, they're giving main character energy 👑💖