Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49287: tpm: fix reference counting for struct tpm_chip

Noroxi assessment

Priority: Monitor (action score 28/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.27% (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 290e05f346d1829e849662c97e42d5ad984f5258, 2f928c0d5c02dbab49e8c19d98725c822f6fc409, 473a66f99cb8173c14138c5a5c69bfad04e8f9ac.

Low priority for now. Upgrade to Linux Linux 290e05f346d1829e849662c97e42d5ad984f5258, 2f928c0d5c02dbab49e8c19d98725c822f6fc409, 473a66f99cb8173c14138c5a5c69bfad04e8f9ac 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: 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 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 [<c0410c3c>] (unwind_backtrace) from [<c040b580>] (show_stack+0x10/0x14) [<c040b580>] (show_stack) from [<c1092174>] (dump_stack+0xc4/0xd8) [<c1092174>] (dump_stack) from [<c0445a30>] (__warn+0x104/0x108) [<c0445a30>] (__warn) from [<c0445aa8>] (warn_slowpath_fmt+0x74/0xb8) [<c0445aa8>] (warn_slowpath_fmt) from [<c08435d0>] (kobject_get+0xa0/0xa4) [<c08435d0>] (kobject_get) from [<bf0a715c>] (tpm_try_get_ops+0x14/0x54 [tpm]) [<bf0a715c>] (tpm_try_get_ops [tpm]) from [<bf0a7d6c>] (tpm_common_write+0x38/0x60 [tpm]) [<bf0a7d6c>] (tpm_common_write [tpm]) from [<c05a7ac0>] (vfs_write+0xc4/0x3c0) [<c05a7ac0>] (vfs_write) from [<c05a7ee4>] (ksys_write+0x58/0xcc) [<c05a7ee4>] (ksys_write) from [<c04001a0>] (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<n>") 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.

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2022-49287

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.12 and later · before 4.14.276
  • linux linux kernel4.15 and later · before 4.19.238
  • linux linux kernel4.20 and later · before 5.4.189
  • linux linux kernel5.5 and later · before 5.10.110
  • linux linux kernel5.11 and later · before 5.15.33
  • linux linux kernel5.16 and later · before 5.16.19
  • linux linux kernel5.17 and later · before 5.17.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

    • 4.12affected
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before 473a66f99cb8173c14138c5a5c69bfad04e8f9acaffected · git
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before cb64bd038beacb4331fe464a36c8b5481e8f51e2affected · git
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before a27ed2f3695baf15f9b34d2d7a1f9fc105539a81affected · git
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before 290e05f346d1829e849662c97e42d5ad984f5258affected · git
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before 662893b4f6bd466ff9e1cd454c44c26d32d554feaffected · git
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before 2f928c0d5c02dbab49e8c19d98725c822f6fc409affected · git
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before 6e7baf84149fb43950631415de231b3a41915aa3affected · git
    • fdc915f7f71939ad5a3dda3389b8d2d7a7c5ee66 and later · before 7e0438f83dc769465ee663bb5dcf8cc154940712affected · git
    • before 4.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.17.3-15.17.3-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:7.2.0-362.8.1.el9_30:7.2.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-develbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3
Red Hat:enterprise_linux:9::appstreamlibperf-debuginfobefore 0:5.14.0-362.8.1.el9_30:5.14.0-362.8.1.el9_3

+55

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49285Feb 26, 2025 · iio: accel: mma8452: use the correct logic to get mma8452_data
    22Monitor
  • ← EarlierCVE-2022-49286Feb 26, 2025 · tpm: use try_get_ops() in tpm-space.c
    18Monitor
  • Later →CVE-2022-49288Feb 26, 2025 · ALSA: pcm: Fix races among concurrent prealloc proc writes
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux290e05f346d1829e849662c97e42d5ad984f5258Vendor (CNA)
Linux Linux2f928c0d5c02dbab49e8c19d98725c822f6fc409Vendor (CNA)
Linux Linux473a66f99cb8173c14138c5a5c69bfad04e8f9acVendor (CNA)
Linux Linux662893b4f6bd466ff9e1cd454c44c26d32d554feVendor (CNA)
Linux Linux6e7baf84149fb43950631415de231b3a41915aa3Vendor (CNA)
Linux Linux7e0438f83dc769465ee663bb5dcf8cc154940712Vendor (CNA)
Linux Linuxa27ed2f3695baf15f9b34d2d7a1f9fc105539a81Vendor (CNA)
Linux Linuxcb64bd038beacb4331fe464a36c8b5481e8f51e2Vendor (CNA)
debian:linux5.17.3-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.2.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-362.8.1.el9_3 · Red Hat:enterprise_linux:9::appstreamPackage 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.

No history yet (it accumulates with the daily EPSS job).

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.

Finders, 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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records