char: tpm: Protect tpm_pm_suspend with locks
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 23393c6461422df5bf8084a086ada9a7e17dc2ba, 25b78bf98b07ff5aceb9b1e24f72ec0236c5c053, 4e0d6c687c925e27fd4bc78a2721d10acf5614d6.
Low priority for now. Upgrade to Linux Linux 23393c6461422df5bf8084a086ada9a7e17dc2ba, 25b78bf98b07ff5aceb9b1e24f72ec0236c5c053, 4e0d6c687c925e27fd4bc78a2721d10acf5614d6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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]
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.1 and later · before 5.4.226
- linux linux kernel5.5 and later · before 5.10.158
- linux linux kernel5.11 and later · before 5.15.82
- linux linux kernel5.16 and later · before 6.0.12
- linux linux kernel6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.1affected
- e891db1a18bf11e02533ec2386b796cfd8d60666 and later · before d699373ac5f3545243d3c73a1ccab77fdef8cec6affected · git
- e891db1a18bf11e02533ec2386b796cfd8d60666 and later · before 4e0d6c687c925e27fd4bc78a2721d10acf5614d6affected · git
- e891db1a18bf11e02533ec2386b796cfd8d60666 and later · before 571b6bbbf54d835ea6120f65575cb55cd767e603affected · git
- e891db1a18bf11e02533ec2386b796cfd8d60666 and later · before 25b78bf98b07ff5aceb9b1e24f72ec0236c5c053affected · git
- e891db1a18bf11e02533ec2386b796cfd8d60666 and later · before 23393c6461422df5bf8084a086ada9a7e17dc2baaffected · git
- before 5.1not affected · semver
- 5.4.226 and later · up to and including 5.4.*not affected · semver
- 5.10.158 and later · up to and including 5.10.*not affected · semver
- 5.15.82 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.12-1 | 6.0.12-1 |
| Red Hat:enterprise_linux:8::baseos | bpftool | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | bpftool-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-abi-stablelists | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-core | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-core | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-devel | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules-extra | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-aarch64 | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-ppc64le | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-s390x | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-x86_64 | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-devel | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-doc | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-modules-extra | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools-debuginfo | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
| Red Hat:enterprise_linux:8::baseos | kernel-tools-libs | before 0:4.18.0-513.5.1.el8_9 | 0:4.18.0-513.5.1.el8_9 |
+89
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 23393c6461422df5bf8084a086ada9a7e17dc2ba | Vendor (CNA) |
| Linux Linux | 25b78bf98b07ff5aceb9b1e24f72ec0236c5c053 | Vendor (CNA) |
| Linux Linux | 4e0d6c687c925e27fd4bc78a2721d10acf5614d6 | Vendor (CNA) |
| Linux Linux | 571b6bbbf54d835ea6120f65575cb55cd767e603 | Vendor (CNA) |
| Linux Linux | d699373ac5f3545243d3c73a1ccab77fdef8cec6 | Vendor (CNA) |
| debian:linux | 6.0.12-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.2.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.