crypto: qat - fix memory leak in RSA
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix memory leak in RSA When an RSA key represented in form 2 (as defined in PKCS #1 V2.1) is used, some components of the private key persist even after the TFM is released. Replace the explicit calls to free the buffers in qat_rsa_exit_tfm() with a call to qat_rsa_clear_ctx() which frees all buffers referenced in the TFM context.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.58, 5.18.15
- CVEs
- CVE-2022-49566
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 10:46 UTC · Revision 1
Source evidence
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix memory leak in RSA When an RSA key represented in form 2 (as defined in PKCS #1 V2.1) is used, some components of the private key persist even after the TFM is released. Replace the explicit calls to free the buffers in qat_rsa_exit_tfm() with a call to qat_rsa_clear_ctx() which frees all buffers referenced in the TFM context.
osv:CVE-2022-49566
Kernel
Fixed versions: 5.15.58, 5.18.15
Complete source record
{
"id": "3b6d5597fabaea849b9b7d19bb685aeda14cbfc4753c51df98a4d43298bbde6b",
"url": "https://osv.dev/vulnerability/CVE-2022-49566",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "crypto: qat - fix memory leak in RSA",
"summary": "In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix memory leak in RSA When an RSA key represented in form 2 (as defined in PKCS #1 V2.1) is used, some components of the private key persist even after the TFM is released. Replace the explicit calls to free the buffers in qat_rsa_exit_tfm() with a call to qat_rsa_clear_ctx() which frees all buffers referenced in the TFM context.",
"evidence": "osv:CVE-2022-49566",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.58",
"evidence": "/affected/1/ranges"
},
{
"value": "5.18.15",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2022-49566",
"aliases": [
"CVE-2022-49566"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "879f77e9071f029e1c9bd5a75814ecf51370f846"
},
{
"fixed": "a843925e0287eebb4aa808666bf22c664dfe4c53"
},
{
"fixed": "0f967fdc09955221a1951a279481b0bf4d359941"
},
{
"fixed": "80a52e1ee7757b742f96bfb0d58f0c14eb6583d0"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49566.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.8.0"
},
{
"fixed": "5.15.58"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.18.15"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49566.json"
}
}
],
"modified": "2026-10-28T02:30:44.147868675Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0f967fdc09955221a1951a279481b0bf4d359941",
"https://git.kernel.org/stable/c/80a52e1ee7757b742f96bfb0d58f0c14eb6583d0",
"https://git.kernel.org/stable/c/a843925e0287eebb4aa808666bf22c664dfe4c53",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49566.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49566",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49566.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49566",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 511666,
"published_at": "2025-02-26T02:23:11.749+00:00"
}