CVE-2026-53055: crypto: hisilicon/sec2 - prevent req used-after-free for sec

Published Jun 24, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

crypto: hisilicon/sec2 - prevent req used-after-free for sec

During packet transmission, if the system is under heavy load, the hardware might complete processing the packet and free the request memory (req) before the transmission function finishes. If the software subsequently accesses this req, a use-after-free error will occur. The qpctx memory exists throughout the packet sending process, so replace the req with the qpctx.

Affected Software

3 affected components
Linux Linux kernel (crypto/hisilicon/sec2)
Linux Linux kernel>=6.17<6.18.33
Linux Linux kernel>=6.19<7.0.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Under heavy load, reduce or mitigate traffic/requests to lower the likelihood of triggering the use-after-free in the Linux kernel crypto hisilicon/sec2 path until the kernel fix is applied.

Event History

Jun 24, 2026
CVE Published
via MITRE·04:30 PM
Data Sourced
via MITRE·04:30 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-53055?

CVE-2026-53055 has a critical severity score of 9.8.

2

What impact does CVE-2026-53055 have on Linux systems?

CVE-2026-53055 can lead to a use-after-free condition affecting packet transmission under heavy load.

3

How do I fix CVE-2026-53055?

To fix CVE-2026-53055, upgrade your Linux kernel to the patched version that addresses this vulnerability.

4

Which Linux kernel versions are affected by CVE-2026-53055?

CVE-2026-53055 affects the Linux kernel's crypto/hisilicon/sec2 component.

5

What mitigation strategies exist for CVE-2026-53055?

There are no specific mitigation strategies for CVE-2026-53055 other than applying the kernel update.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203