CVE-2022-49627: ima: Fix potential memory leak in ima_init_crypto()

Published Feb 26, 2025
·
Updated

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

ima: Fix potential memory leak in imainitcrypto()

On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing the imaalgoarray. Add the missing kfree() for imaalgoarray to avoid the potential memory leak.

Affected Software

14 affected components
Linux Kernel
Linux Linux kernel>=5.8<5.10.132
Linux Linux kernel>=5.11<5.15.56
Linux Linux kernel>=5.16<5.18.13
Linux Linux kernel=5.19-rc1
Linux Linux kernel=5.19-rc2
Linux Linux kernel=5.19-rc3
Linux Linux kernel=5.19-rc4
Linux Linux kernel=5.19-rc5
Linux Linux kernel=5.19-rc6
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In ima_init_crypto(), ensure that when allocation of the SHA1 tfm fails and IMA exits, the code frees ima_algo_array (add the missing kfree) to avoid the potential memory leak.

    Linux kernel IMA (ima_init_crypto / ima_algo_array) memory management (add missing kfree) = kfree(ima_algo_array) on failure to allocate SHA1 tfm

Event History

Feb 26, 2025
CVE Published
via MITRE·02:23 AM
Data Sourced
via MITRE·02:23 AM
Description
Data Sourced
via Red Hat·03:09 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:01 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-2022-49627?

CVE-2022-49627 has been classified as a low-severity vulnerability due to the potential memory leak issue in the Linux kernel.

2

How do I fix CVE-2022-49627?

To fix CVE-2022-49627, upgrade to a version of the Linux kernel that contains the patch addressing the memory leak issue.

3

What versions of the Linux kernel are affected by CVE-2022-49627?

CVE-2022-49627 affects various versions of the Linux kernel from 5.8 to 5.19-rc6.

4

What impact does CVE-2022-49627 have on system performance?

CVE-2022-49627 may cause reduced system performance over time due to a possible memory leak.

5

Is CVE-2022-49627 a remote exploit risk?

CVE-2022-49627 does not represent a direct remote exploit risk as it requires local execution to trigger the memory leak.

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