aes_cbc_cts_decrypt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ aes_cbc_cts_decrypt(9) β€” NAME ✨

okay so bestie, welcome to the Kernel API Manual πŸ’… this page is literally all about aes_cbc_cts_decrypt β€” the function that decrypts your data using AES-CBC-CTS (the CS3 variant, iykyk πŸ¦‹). no cap, that's the whole vibe.


🌸 SYNOPSIS 🌸

void aes_cbc_cts_decrypt (u8 *dst , const u8 *src , size_t len , u8
iv[static AES_BLOCK_SIZE] , const struct aes_key *key );

that's the whole signature, periodt πŸŽ€


πŸ’– ARGUMENTS πŸ’–

  • dst β€” the destination buffer, aka where the decrypted goodness lands. it can be in-place or out-of-place, both are totally fine 🫢. but for any other kind of overlap? nope β€” the behaviour is unspecified πŸ™ˆ so like, don't do that, bestie, fr fr.
  • src β€” the source data. the ciphertext. the thing you're decrypting. literally the main character of this whole operation πŸ‘‘.
  • len β€” number of bytes to decrypt. and listen, it must be at least AES_BLOCK_SIZE β€” no tiny little sliver of a buffer, okay? πŸ’€
  • iv β€” the initialization vector. heads up though: it gets clobbered by this function 😭 like it just straight-up gets wrecked in the process, so don't come back expecting to find it the way you left it.
  • key β€” the key. and it has to already be prepared using aes_preparekey β€” do that first, don't skip ahead 🧚.

⭐ CONTEXT ⭐

Any context. yup, that's it β€” anywhere, any context, she's flexible like that πŸ’œ.


πŸ”₯ SEE ALSO πŸ”₯

go read those too if you wanna be an AES-CBC-CTS scholar, ngl 🌈


and finally, the cute lil sign-off πŸ’Œ: this page lives under ./include/crypto, and it's dated October 2026 β€” slay, we love a documented kernel function πŸŽ€βœ¨πŸ’–

πŸ“¦ where this page comes from