char: tpm: Protect tpm_pm_suspend with locks
In the Linux kernel, the following vulnerability has been resolved: char: tpm: Protect tpm_pm_suspend with locks Currently tpm transactions are executed unconditionally in tpm_pm_suspend() function, which may lead to races with other tpm accessors in the system. Specifically, the hw_random tpm driver makes use of tpm_get_random(), and this function is called in a loop from a kthread, which means it's not frozen alongside userspace, and so can race with the work done during system suspend: tpm tpm0: tpm_transmit: tpm_recv: error -52 tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics CPU: 0 PID: 1 Comm: init Not tainted 6.1.0-rc5+ #135 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Call Trace: tpm_tis_status.cold+0x19/0x20 tpm_transmit+0x13b/0x390 tpm_transmit_cmd+0x20/0x80 tpm1_pm_suspend+0xa6/0x110 tpm_pm_suspend+0x53/0x80 __pnp_bus_suspend+0x35/0xe0 __device_suspend+0x10f/0x350 Fix this by calling tpm_try_get_ops(), which itself is a wrapper around tpm_chip_start(), but takes the appropriate mutex. [Jason: reworked commit message, added metadata]
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.158, 5.15.82, 5.4.226, 6.0.12
- CVEs
- CVE-2022-48997
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 02:54 UTC · Revision 1
Source evidence
char: tpm: Protect tpm_pm_suspend with locks
core-osv · Original sourcePublished 21 Oct 2024, 20:06 UTC
In the Linux kernel, the following vulnerability has been resolved: char: tpm: Protect tpm_pm_suspend with locks Currently tpm transactions are executed unconditionally in tpm_pm_suspend() function, which may lead to races with other tpm accessors in the system. Specifically, the hw_random tpm driver makes use of tpm_get_random(), and this function is called in a loop from a kthread, which means it's not frozen alongside userspace, and so can race with the work done during system suspend: tpm tpm0: tpm_transmit: tpm_recv: error -52 tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics CPU: 0 PID: 1 Comm: init Not tainted 6.1.0-rc5+ #135 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Call Trace: tpm_tis_status.cold+0x19/0x20 tpm_transmit+0x13b/0x390 tpm_transmit_cmd+0x20/0x80 tpm1_pm_suspend+0xa6/0x110 tpm_pm_suspend+0x53/0x80 __pnp_bus_suspend+0x35/0xe0 __device_suspend+0x10f/0x350 Fix this by calling tpm_try_get_ops(), which itself is a wrapper around tpm_chip_start(), but takes the appropriate mutex. [Jason: reworked commit message, added metadata]
osv:CVE-2022-48997
Kernel
Fixed versions: 5.4.226, 5.10.158, 5.15.82, 6.0.12
Complete source record
{
"id": "3cee924a5be39d9fc4cc855dc76cc5fc3d993bb76523d9643a892a05fc5df78a",
"url": "https://osv.dev/vulnerability/CVE-2022-48997",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "char: tpm: Protect tpm_pm_suspend with locks",
"summary": "In the Linux kernel, the following vulnerability has been resolved: char: tpm: Protect tpm_pm_suspend with locks Currently tpm transactions are executed unconditionally in tpm_pm_suspend() function, which may lead to races with other tpm accessors in the system. Specifically, the hw_random tpm driver makes use of tpm_get_random(), and this function is called in a loop from a kthread, which means it's not frozen alongside userspace, and so can race with the work done during system suspend: tpm tpm0: tpm_transmit: tpm_recv: error -52 tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics CPU: 0 PID: 1 Comm: init Not tainted 6.1.0-rc5+ #135 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-20220807_005459-localhost 04/01/2014 Call Trace: tpm_tis_status.cold+0x19/0x20 tpm_transmit+0x13b/0x390 tpm_transmit_cmd+0x20/0x80 tpm1_pm_suspend+0xa6/0x110 tpm_pm_suspend+0x53/0x80 __pnp_bus_suspend+0x35/0xe0 __device_suspend+0x10f/0x350 Fix this by calling tpm_try_get_ops(), which itself is a wrapper around tpm_chip_start(), but takes the appropriate mutex. [Jason: reworked commit message, added metadata]",
"evidence": "osv:CVE-2022-48997",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.226",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.158",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.82",
"evidence": "/affected/1/ranges"
},
{
"value": "6.0.12",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-48997",
"aliases": [
"CVE-2022-48997"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "e891db1a18bf11e02533ec2386b796cfd8d60666"
},
{
"fixed": "d699373ac5f3545243d3c73a1ccab77fdef8cec6"
},
{
"fixed": "4e0d6c687c925e27fd4bc78a2721d10acf5614d6"
},
{
"fixed": "571b6bbbf54d835ea6120f65575cb55cd767e603"
},
{
"fixed": "25b78bf98b07ff5aceb9b1e24f72ec0236c5c053"
},
{
"fixed": "23393c6461422df5bf8084a086ada9a7e17dc2ba"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48997.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.1.0"
},
{
"fixed": "5.4.226"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.158"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.82"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.0.12"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48997.json"
}
}
],
"modified": "2026-10-28T02:30:53.386338745Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/23393c6461422df5bf8084a086ada9a7e17dc2ba",
"https://git.kernel.org/stable/c/25b78bf98b07ff5aceb9b1e24f72ec0236c5c053",
"https://git.kernel.org/stable/c/4e0d6c687c925e27fd4bc78a2721d10acf5614d6",
"https://git.kernel.org/stable/c/571b6bbbf54d835ea6120f65575cb55cd767e603",
"https://git.kernel.org/stable/c/d699373ac5f3545243d3c73a1ccab77fdef8cec6",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48997.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-48997",
"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/48xxx/CVE-2022-48997.json"
}
},
"related_cves": [
{
"value": "CVE-2022-48997",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 521980,
"published_at": "2024-10-21T20:06:12.787+00:00"
}