{"uuid": "afe7e3df-40ee-43e0-a768-263efc3719d3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53085", "type": "seen", "source": "https://t.me/cvedetector/11487", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-53085 - \"Linux Tpm Lock Discipline Info Disclosure\"\", \n  \"Content\": \"CVE ID : CVE-2024-53085 \nPublished : Nov. 19, 2024, 6:15 p.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ntpm: Lock TPM chip in tpm_pm_suspend() first  \n  \nSetting TPM_CHIP_FLAG_SUSPENDED in the end of tpm_pm_suspend() can be racy  \naccording, as this leaves window for tpm_hwrng_read() to be called while  \nthe operation is in progress. The recent bug report gives also evidence of  \nthis behaviour.  \n  \nAadress this by locking the TPM chip before checking any chip->flags both  \nin tpm_pm_suspend() and tpm_hwrng_read(). Move TPM_CHIP_FLAG_SUSPENDED  \ncheck inside tpm_get_random() so that it will be always checked only when  \nthe lock is reserved. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-19T20:09:47.000000Z"}