security_locked_down(9)

📦 version 7.3.1, in nixpkgs unstable

💖 security_locked_down(9) 💖

ok so welcome to the Kernel API Manual, bestie 🫶 this is the page for security_locked_down, and yes it's exactly as dramatic as it sounds. grab a snack, we're doing one (1) very important function.

✨ NAME ✨

security_locked_down — the vibe check for whether a kernel feature is allowed 💅

🌸 SYNOPSIS 🌸

int security_locked_down (enum lockdown_reason what );

🎀 ARGUMENTS 🎀

  • what — the kernel feature you're asking about. like, the actual thing being requested, specified as an enum lockdown_reason 👑

🦋 DESCRIPTION 🦋

okay so here's the tea 🍓 this function determines whether a kernel feature that potentially enables arbitrary code execution in kernel space should be permitted.

read that again. arbitrary. code. execution. in. kernel. space. 💀 that's the whole reason this function exists, and it's lowkey the most main-character thing in the entire LSM layer. it's literally the bouncer at the club and the club is ring zero 🔥

⭐ RETURN ⭐

Returns 0 if permission is granted. that's it, that's the return value, and honestly? iconic. ✨

💜 SEE ALSO 💜

no cap this list is long, but every single one of these is real and you're gonna need them, so here we go 🧚 it all lives in the kernel file ./security/security.c:

and that's the whole page, bestie 🎀 big slay, no notes. this one came out of ./security, dated October 2026 — mwah, drink some water, and go read the source 💖✨🦋

📦 where this page comes from