aes_ccm_encrypt_update(9)

✨ aes_ccm_encrypt_update ✨

okay bestie gather round, we're looking at the aes_ccm_encrypt_update(9) page from the Kernel API Manual (section 9, iykyk) and honestly? it's giving "short but mighty" 💅

---

🌸 NAME 🌸

aes_ccm_encrypt_update — the lowkey icon that lets you incrementally encrypt data with AES-CCM ✨

---

🦋 SYNOPSIS 🦋

void aes_ccm_encrypt_update (struct aes_ccm_ctx *ctx , u8 *dst , const
u8 *src , size_t len );

---

🎀 ARGUMENTS 🎀

• ctx — an AES-CCM context 🫶 your whole vibe lives here
• dst — the destination buffer 💖 and yes it can be in-place or out-of-place, she's flexible like that. but for other overlaps? the behavior is unspecified 😭 so pls don't, that's not the main character move
• src — the source plaintext data 🌸 the raw material, the moment before the glow-up
• len — number of bytes to encrypt 💫 count them, bestie

---

💜 DESCRIPTION 💜

okay so the rules are rules:

• You can call this only after all associated data has been processed ✋ no skipping ahead, this is a sequence
• The total length of the encrypted data (over all calls to this function, so like, the running total across every single call) MUST match the data_len that was passed to aes_ccm_init 👑 no cap, mismatch = not it

🚨 that capital-M MUST is doing a lot of heavy lifting — get the length wrong and the whole thing falls apart fr fr

---

🌈 CONTEXT 🌈

Any context. literally any. she's adaptable ✨💅

---

⭐ SEE ALSO ⭐

• Kernel file ./include/crypto/aes-ccm.h
• struct aes_ccm_key(9)
• struct aes_ccm_ctx(9)
• aes_ccm_preparekey(9)
• aes_ccm_encrypt(9)
• aes_ccm_decrypt(9)
• aes_ccm_init(9)
• aes_ccm_auth_update(9)
• aes_ccm_decrypt_update(9)
• aes_ccm_encrypt_final(9)
• aes_ccm_decrypt_final(9)

the whole friend group, honestly 🫶 go read them all

---

and that's the page!! brought to you by ./include/crypto, dated October 2026, manual name aes_ccm_encrypt_update(9) 💖 mwah, slay, go encrypt responsibly ✨🎀🦋