CVE-2022-48997

See a problem?
Please try reporting it to the source first.
Source
https://nvd.nist.gov/vuln/detail/CVE-2022-48997
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-48997.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-48997
Related
Published
2024-10-21T20:15:11Z
Modified
2024-11-07T18:46:03.611437Z
Severity
  • 4.7 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
[none]
Details

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

char: tpm: Protect tpmpmsuspend with locks

Currently tpm transactions are executed unconditionally in tpmpmsuspend() function, which may lead to races with other tpm accessors in the system.

Specifically, the hwrandom tpm driver makes use of tpmget_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: tpmtransmit: tpmrecv: error -52 tpm tpm0: invalid TPMSTS.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-20220807005459-localhost 04/01/2014 Call Trace: tpmtisstatus.cold+0x19/0x20 tpmtransmit+0x13b/0x390 tpmtransmitcmd+0x20/0x80 tpm1pmsuspend+0xa6/0x110 tpmpmsuspend+0x53/0x80 _pnpbussuspend+0x35/0xe0 _devicesuspend+0x10f/0x350

Fix this by calling tpmtrygetops(), which itself is a wrapper around tpmchip_start(), but takes the appropriate mutex.

[Jason: reworked commit message, added metadata]

References

Affected packages

Debian:11 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.10.158-1

Affected versions

5.*

5.10.46-4
5.10.46-5
5.10.70-1~bpo10+1
5.10.70-1
5.10.84-1
5.10.92-1~bpo10+1
5.10.92-1
5.10.92-2
5.10.103-1~bpo10+1
5.10.103-1
5.10.106-1
5.10.113-1
5.10.120-1~bpo10+1
5.10.120-1
5.10.127-1
5.10.127-2~bpo10+1
5.10.127-2
5.10.136-1
5.10.140-1
5.10.148-1
5.10.149-1
5.10.149-2

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.0.12-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.0.12-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}