Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48997

char: tpm: Protect tpm_pm_suspend with locks

Medium4.7EPSS 0.24%
Published
Updated
Reserved
Assigned by
Linux

Description

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]

Scores

CVSS scores of CVE-2022-48997, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected e891db1a18bf11e02533ec2386b796cfd8d60666 – < d699373ac5f3545243d3c73a1ccab77fdef8cec6
    • affected e891db1a18bf11e02533ec2386b796cfd8d60666 – < 4e0d6c687c925e27fd4bc78a2721d10acf5614d6
    • affected e891db1a18bf11e02533ec2386b796cfd8d60666 – < 571b6bbbf54d835ea6120f65575cb55cd767e603
    • affected e891db1a18bf11e02533ec2386b796cfd8d60666 – < 25b78bf98b07ff5aceb9b1e24f72ec0236c5c053
    • affected e891db1a18bf11e02533ec2386b796cfd8d60666 – < 23393c6461422df5bf8084a086ada9a7e17dc2ba
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.4.226 – ≤ 5.4.*
    • unaffected 5.10.158 – ≤ 5.10.*
    • unaffected 5.15.82 – ≤ 5.15.*
    • unaffected 6.0.12 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48997 badge
[![CVE-2022-48997](https://trackcve.app/badge/CVE-2022-48997.svg)](https://trackcve.app/cve/CVE-2022-48997)

Record last updated .