dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53016

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.10.258 / 5.15.209 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - copy IV using skcipher ivsize AF_ALG rfc3686-ctr-aes-ccp requests pass an 8-byte IV to the driver. ccp_aes_complete() restores AES_BLOCK_SIZE bytes into the caller's IV buffer while RFC3686 skciphers expose an 8-byte IV, so the restore overruns the provided buffer. Use crypto_skcipher_ivsize() to copy only the algorithm's IV length.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel crypto CCP driver, ccp_aes_complete() writes AES_BLOCK_SIZE (16 bytes) back to the caller's IV buffer, but RFC3686 skciphers only provide an 8-byte IV. This causes a buffer overflow when restoring the IV, as 16 bytes are written into an 8-byte buffer.

MitigationApply the kernel patch that uses crypto_skcipher_ivsize() to copy only the algorithm's actual IV length instead of the fixed AES_BLOCK_SIZE. This is a single code change in the ccp_aes_complete() function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 3.14, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run 'uname -r' or view /proc/version to obtain the running kernel version
    Affected if The kernel version falls within one of these ranges: >= 3.14 and < 5.10.258; >= 5.11 and < 5.15.209; >= 5.16 and < 6.1.175; >= 6.2 and < 6.6.141; >= 6.7 and < 6.12.91; >= 6.13 and < 6.18.33; >= 6.19 and < 7.0.10
  2. Verify CCP crypto driver is present
    Check /proc/crypto for 'ccp' entry, or run 'lsmod | grep ccp' to see if the CCP kernel module is loaded
    Affected if The CCP driver is present and handles AES cryptographic operations in the kernel
  3. Identify RFC3686 cipher usage
    Search /proc/crypto for 'rfc3686' or 'ctr' cipher entries, or examine active IPsec/security configurations using 'ip xfrm state' or similar tools
    Affected if AES in CTR mode (RFC3686) is being used for IPsec or other cryptographic operations handled by the CCP driver

Your environment is affected if you are running a kernel version within the affected ranges AND the CCP crypto driver is loaded AND you are using AES in RFC3686/CTR mode for active cryptographic operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.258 / 5.15.209 / 6.1.175 or later
Fixed in 5.10.2585.15.2096.1.175
Interim mitigation

Apply the kernel patch that uses crypto_skcipher_ivsize() to copy only the algorithm's actual IV length instead of the fixed AES_BLOCK_SIZE. This is a single code change in the ccp_aes_complete() function.

Recommended fix High confidence

5.10.258, 5.15.209, 6.1.175, or 6.6.141 (depending on which major kernel branch you are on)

  1. 1. Identify the currently running kernel version using `uname -r`
  2. 2. Determine the appropriate fixed kernel version based on your current major version: for 5.10.x use 5.10.258+, for 5.11-5.15.x use 5.15.209+, for 5.16-6.1.x use 6.1.175+, for 6.2-6.6.x use 6.6.141+
  3. 3. Update the kernel package via your distribution's package manager (e.g., `apt-get update && apt-get install linux-image-<version>` for Debian/Ubuntu, or `yum update kernel` for RHEL/CentOS)
  4. 4. Reboot the system to load the patched kernel
  5. 5. Verify the running kernel version with `uname -r` to confirm the fix is applied
Caveat Kernel upgrades may require rebuilding third-party kernel modules (like proprietary drivers); ensure compatibility testing in non-production environments first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53016 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data