CVE-2022-49287

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2022-54939 (ENISA EUVD) · GHSA-gc4f-hpr3-xwmc (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tpm: fix reference counting for struct tpm_chip

The following sequence of operations results in a refcount warning:

  • Open device /dev/tpmrm.
  • Remove module tpm_tis_spi.
  • Write a TPM command to the file descriptor opened at step 1.

------------[ cut here ]------------ WARNING: CPU: 3 PID: 1161 at lib/refcount.c:25 kobject_get+0xa0/0xa4 refcount_t: addition on 0; use-after-free. Modules linked in: tpm_tis_spi tpm_tis_core tpm mdio_bcm_unimac brcmfmac sha256_generic libsha256 sha256_arm hci_uart btbcm bluetooth cfg80211 vc4 brcmutil ecdh_generic ecc snd_soc_core crc32_arm_ce libaes raspberrypi_hwmon ac97_bus snd_pcm_dmaengine bcm2711_thermal snd_pcm snd_timer genet snd phy_generic soundcore [last unloaded: spi_bcm2835] CPU: 3 PID: 1161 Comm: hold_open Not tainted 5.10.0ls-main-dirty #2 Hardware name: BCM2711 [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (dump_stack+0xc4/0xd8) [] (dump_stack) from [] (__warn+0x104/0x108) [] (__warn) from [] (warn_slowpath_fmt+0x74/0xb8) [] (warn_slowpath_fmt) from [] (kobject_get+0xa0/0xa4) [] (kobject_get) from [] (tpm_try_get_ops+0x14/0x54 [tpm]) [] (tpm_try_get_ops [tpm]) from [] (tpm_common_write+0x38/0x60 [tpm]) [] (tpm_common_write [tpm]) from [] (vfs_write+0xc4/0x3c0) [] (vfs_write) from [] (ksys_write+0x58/0xcc) [] (ksys_write) from [] (ret_fast_syscall+0x0/0x4c) Exception stack(0xc226bfa8 to 0xc226bff0) bfa0: 00000000 000105b4 00000003 beafe664 00000014 00000000 bfc0: 00000000 000105b4 000103f8 00000004 00000000 00000000 b6f9c000 beafe684 bfe0: 0000006c beafe648 0001056c b6eb6944 ---[ end trace d4b8409def9b8b1f ]---

The reason for this warning is the attempt to get the chip->dev reference in tpm_common_write() although the reference counter is already zero.

Since commit 8979b02aaf1d ("tpm: Fix reference count to main device") the extra reference used to prevent a premature zero counter is never taken, because the required TPM_CHIP_FLAG_TPM2 flag is never set.

Fix this by moving the TPM 2 character device handling from tpm_chip_alloc() to tpm_add_char_device() which is called at a later point in time when the flag has been set in case of TPM2.

Commit fdc915f7f719 ("tpm: expose spaces via a device link /dev/tpmrm") already introduced function tpm_devs_release() to release the extra reference but did not implement the required put on chip->devs that results in the call of this function.

Fix this by putting chip->devs in tpm_chip_unregister().

Finally move the new implementation for the TPM 2 handling into a new function to avoid multiple checks for the TPM_CHIP_FLAG_TPM2 flag in the good case and error cases.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 4, 2026
Patch available.
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cb64bd038beacb4331fe464a36c8b5481e8f51e2
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a27ed2f3695baf15f9b34d2d7a1f9fc105539a81
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e0438f83dc769465ee663bb5dcf8cc154940712
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e7baf84149fb43950631415de231b3a41915aa3
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/662893b4f6bd466ff9e1cd454c44c26d32d554fe
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/473a66f99cb8173c14138c5a5c69bfad04e8f9ac
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f928c0d5c02dbab49e8c19d98725c822f6fc409
Web page

tpm: fix reference counting for struct tpm_chip - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/290e05f346d1829e849662c97e42d5ad984f5258

Vendor Advisories for CVE-2022-49287(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.14.276 (fixes >=4.12.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (11 versions)
  • every version up to 5.10.113-1: fixed in 5.10.113-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 202 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-27 21:19 UTCEG score recompute
  7. 2026-10-27 21:19 UTCGHSA enrichmentGHSA-gc4f-hpr3-xwmc · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-25 17:55 UTCEG score recompute
  11. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-21 05:36 UTCEG score recompute
  17. 2026-10-21 05:36 UTCGHSA enrichmentGHSA-gc4f-hpr3-xwmc · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-19 12:25 UTCOSV refresh
  21. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-18 08:20 UTCEG score recompute
  23. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 73 more
  1. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-12 18:42 UTCEG score recompute
  4. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-11 22:05 UTCEG score recompute
  6. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-09-30 16:12 UTCEG score recompute
  16. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-09-26 19:03 UTCOSV refresh
  19. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  27. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  28. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  29. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  30. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  31. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  32. 2026-09-07 04:48 UTCOSV refresh
  33. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  34. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  35. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  36. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  37. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  38. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  39. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  40. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  41. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  42. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  43. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  44. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  45. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  46. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  47. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-08-20 14:31 UTCOSV refresh
  49. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  50. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  51. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  52. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  53. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  54. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  55. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  56. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  57. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  59. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  60. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  61. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  62. 2026-08-05 09:32 UTCEG score recompute
  63. 2026-08-05 09:32 UTCGHSA enrichmentGHSA-gc4f-hpr3-xwmc · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  65. 2026-08-04 11:14 UTCEG score recompute
  66. 2026-08-04 11:14 UTCGHSA enrichmentGHSA-gc4f-hpr3-xwmc · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  68. 2026-08-04 09:46 UTCEG score recompute
  69. 2026-08-04 09:46 UTCGHSA enrichmentGHSA-gc4f-hpr3-xwmc · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  71. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  72. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  73. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49287?
CVE-2022-49287 is a high-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: tpm: fix reference counting for struct tpm_chip The following sequence of operations results in a refcount warning: 1. Open device /dev/tpmrm. 2. Remove module tpm_tis_spi. 3. Write a TPM command to the file descriptor opened at…
When was the CVE record for CVE-2022-49287 published?
The CVE record for CVE-2022-49287 was published on February 26, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-49287 actively exploited?
CVE-2022-49287 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49287?
CVE-2022-49287 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49287?
A fix for CVE-2022-49287 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49287 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49287

Explore →

Is Your Infrastructure Affected by CVE-2022-49287?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs