security_sctp_sk_clone(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– security_sctp_sk_clone(9) β€” Kernel API Manual, section 9 πŸ’–

okay bestie, welcome to the kernel API manual, section 9. this page is all about cloning a SCTP sock's LSM state. it's niche, it's iconic, it's giving security-hook main character energy. πŸ’…

🌸 NAME 🌸

security_sctp_sk_clone β€” Clone a SCTP sock's LSM state

✨ SYNOPSIS ✨

void security_sctp_sk_clone (struct sctp_association *asoc , struct sock *sk , struct sock *newsk );

πŸŽ€ ARGUMENTS πŸŽ€

  • asoc β€” the SCTP association. yes, the whole association, not just a vibe. 🫢
  • sk β€” the original sock. the one you're cloning from, bestie.
  • newsk β€” the target sock. the fresh new sock getting the cloned LSM state. ✨

πŸ’… DESCRIPTION πŸ’…

So this hook gets called whenever a new socket is created by accept(2) β€” that's the TCP-style socket, iykyk β€” or when a socket gets 'peeled off', like when userspace calls sctp_peeloff(3). Basically it's the moment where the LSM state gets cloned over to the new sock. literally the security hook doing a little copy-paste with main character energy. no cap. πŸ’…βœ¨

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./security/security.c β€” and the whole extended fam, fr fr:


that's literally the whole SEE ALSO squad, bestie. I didn't skip a single one. πŸ’€βœ¨

Source: ./security Β· October 2026 Β· that's the tea, no cap. stay sliving, and may your LSM state always clone correctly. πŸ«ΆπŸ’–πŸŽ€

πŸ“¦ where this page comes from