aes_cbc_cts_encrypt(9)

✨ aes_cbc_cts_encrypt(9) ✨

okay so bestie, this one lives in the Kernel API Manual and it's literally the glow-up function for encrypting your data with AES-CBC-CTS (CS3 variant) 💅 — the CTS stands for ciphertext stealing and yes she ate 💖

---

🎀 NAME 🎀

aes_cbc_cts_encrypt — encrypt data using AES-CBC-CTS (CS3 variant), no cap ✨

---

🦋 SYNOPSIS 🦋

void aes_cbc_cts_encrypt (u8 *dst , const u8 *src , size_t len , u8
iv[static AES_BLOCK_SIZE] , aes_encrypt_arg key );

like, that's the whole signature, she's not that complicated 🫶

---

🌸 ARGUMENTS 🌸

• dst — the destination buffer, i.e. where the encrypted vibes go 💫. It can be in-place or out-of-place, super chill. But for any other overlap? ngl the behavior is unspecified — so don't be messy about it, okay? 😭
• src — the source data, the raw material, the main character 🎀
• len — number of bytes to encrypt, and it must be at least AES_BLOCK_SIZE — like, minimum effort is required, periodt 💅
• iv — the initialization vector. Heads up: it gets clobbered by this function 😳 so don't come back looking for it, she's gone 🙈
• key — the key, and it has to be already prepared using aes_preparekey or aes_prepareenckey — no raw keys allowed, that's the rule 🔑✨

---

⭐ CONTEXT ⭐

Any context. literally any. she's flexible like that 🧚

---

🌈 SEE ALSO 🌈

• Kernel file ./include/crypto/aes-cbc.h
• aes_cbc_encrypt(9)
• aes_cbc_decrypt(9)
• aes_cbc_cts_decrypt(9)

go read those too, iykyk 👑🔥

---

ok that's the whole page bestie 💖 don't forget: len ≥ AES_BLOCK_SIZE, your iv is getting clobbered, and weird overlaps are on you 🙈

---

mwah 💋 this page came from the kernel source dir ./include/crypto, dated October 2026 — stamped and slayed, fr fr 🦋✨🎀