CVE-2026-53016

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
3.8%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eecee15e263ccb8cd77170a56ab6c969cb54dd6a
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfb2cf434829819268fe50f41542aad318ad62b2
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/df9784bb5b637ac80f4a2768a58ca9a50bef28a9
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb01d8f1f385bc9034ca114d3508c7fdea24fc9a
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a7a1f3cdd64d8a165d9b8c9e9ad7fb46ac19dfc4
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/939061b2d0f7f15114e34b4ce878ef50ff4089c3
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/798d409a8949f3f495f238549b86de2886b129bd
generic

crypto: ccp - copy IV using skcipher ivsize - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/227c1e1d9e2aa4cfc65ba446d5690da1f546cda4

Vendor Advisories for CVE-2026-53016(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.34.1.el10_22026-07-14redhat
redhatkernel-0:5.14.0-687.25.1.el9_82026-07-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 82× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 03:32 UTCVendor advisory
  8. 2026-07-17 03:32 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 16:24 UTCVendor advisory
  11. 2026-07-16 16:24 UTCGHSA enrichment
  12. 2026-07-16 04:38 UTCVendor advisory
  13. 2026-07-16 04:38 UTCGHSA enrichment
  14. 2026-07-15 17:39 UTCVendor advisory
  15. 2026-07-15 17:39 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 06:28 UTCVendor advisory
  19. 2026-07-15 06:28 UTCGHSA enrichment
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 19:29 UTCVendor advisory
  23. 2026-07-14 19:29 UTCGHSA enrichment
  24. 2026-07-14 08:28 UTCVendor advisory
  25. 2026-07-14 08:27 UTCGHSA enrichment
Show 57 more
  1. 2026-07-13 22:31 UTCEPSS rescore
  2. 2026-07-13 21:22 UTCGHSA enrichment
  3. 2026-07-13 10:20 UTCGHSA enrichment
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 23:21 UTCGHSA enrichment
  7. 2026-07-12 12:22 UTCGHSA enrichment
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-12 01:23 UTCGHSA enrichment
  10. 2026-07-11 14:24 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 03:23 UTCGHSA enrichment
  14. 2026-07-10 16:23 UTCGHSA enrichment
  15. 2026-07-10 05:24 UTCGHSA enrichment
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 18:24 UTCGHSA enrichment
  19. 2026-07-09 07:23 UTCGHSA enrichment
  20. 2026-07-08 20:21 UTCGHSA enrichment
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 09:16 UTCGHSA enrichment
  24. 2026-07-07 22:18 UTCGHSA enrichment
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-07 13:46 UTCEPSS rescore
  27. 2026-07-07 11:18 UTCGHSA enrichment
  28. 2026-07-07 00:19 UTCGHSA enrichment
  29. 2026-07-06 13:20 UTCGHSA enrichment
  30. 2026-07-06 02:23 UTCEPSS rescore
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-06 01:56 UTCGHSA enrichment
  33. 2026-07-05 14:57 UTCGHSA enrichment
  34. 2026-07-05 03:58 UTCGHSA enrichment
  35. 2026-07-04 16:56 UTCGHSA enrichment
  36. 2026-07-04 06:31 UTCEPSS rescore
  37. 2026-07-04 05:57 UTCGHSA enrichment
  38. 2026-07-03 18:57 UTCGHSA enrichment
  39. 2026-07-03 07:58 UTCGHSA enrichment
  40. 2026-07-02 20:57 UTCGHSA enrichment
  41. 2026-07-02 09:58 UTCGHSA enrichment
  42. 2026-07-01 22:59 UTCGHSA enrichment
  43. 2026-07-01 12:00 UTCGHSA enrichment
  44. 2026-07-01 01:01 UTCEG score recompute▲ 7.80
  45. 2026-07-01 01:01 UTCGHSA enrichment
  46. 2026-06-30 23:22 UTCEPSS rescore
  47. 2026-06-29 14:06 UTCEPSS rescore
  48. 2026-06-29 14:06 UTCEPSS rescore
  49. 2026-06-28 14:07 UTCEPSS rescore
  50. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  51. 2026-06-28 04:56 UTCEPSS rescore
  52. 2026-06-28 04:56 UTCEPSS rescore
  53. 2026-06-27 21:41 UTCGHSA enrichment
  54. 2026-06-27 03:08 UTCEPSS rescore
  55. 2026-06-25 13:49 UTCEPSS rescore
  56. 2026-06-24 18:21 UTCEG score recompute
  57. 2026-06-24 18:02 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53016?
CVE-2026-53016 is a high vulnerability published on June 24, 2026. 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. ccpaescomplete() restores AESBLOCKSIZE bytes into the caller's IV buffer while RFC3686 skciphers expose an 8-byte IV,…
When was CVE-2026-53016 disclosed?
CVE-2026-53016 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53016 actively exploited?
CVE-2026-53016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53016?
CVE-2026-53016 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53016, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53016

Explore →

Is Your Infrastructure Affected by CVE-2026-53016?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs