CVE-2021-47097

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2024-03-04. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2021-33745 (ENISA EUVD) · GHSA-cv83-m6f4-pc7m (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Input: elantech - fix stack out of bound access in elantech_change_report_id()

The array param[] in elantech_change_report_id() must be at least 3 bytes, because elantech_read_reg_params() is calling ps2_command() with PSMOUSE_CMD_GETINFO, that is going to access 3 bytes from param[], but it's defined in the stack as an array of 2 bytes, therefore we have a potential stack out-of-bounds access here, also confirmed by KASAN:

[ 6.512374] BUG: KASAN: stack-out-of-bounds in __ps2_command+0x372/0x7e0 [ 6.512397] Read of size 1 at addr ffff8881024d77c2 by task kworker/2:1/118

[ 6.512416] CPU: 2 PID: 118 Comm: kworker/2:1 Not tainted 5.13.0-22-generic #22+arighi20211110 [ 6.512428] Hardware name: LENOVO 20T8000QGE/20T8000QGE, BIOS R1AET32W (1.08 ) 08/14/2020 [ 6.512436] Workqueue: events_long serio_handle_event [ 6.512453] Call Trace: [ 6.512462] show_stack+0x52/0x58 [ 6.512474] dump_stack+0xa1/0xd3 [ 6.512487] print_address_description.constprop.0+0x1d/0x140 [ 6.512502] ? __ps2_command+0x372/0x7e0 [ 6.512516] __kasan_report.cold+0x7d/0x112 [ 6.512527] ? _raw_write_lock_irq+0x20/0xd0 [ 6.512539] ? __ps2_command+0x372/0x7e0 [ 6.512552] kasan_report+0x3c/0x50 [ 6.512564] __asan_load1+0x6a/0x70 [ 6.512575] __ps2_command+0x372/0x7e0 [ 6.512589] ? ps2_drain+0x240/0x240 [ 6.512601] ? dev_printk_emit+0xa2/0xd3 [ 6.512612] ? dev_vprintk_emit+0xc5/0xc5 [ 6.512621] ? __kasan_check_write+0x14/0x20 [ 6.512634] ? mutex_lock+0x8f/0xe0 [ 6.512643] ? __mutex_lock_slowpath+0x20/0x20 [ 6.512655] ps2_command+0x52/0x90 [ 6.512670] elantech_ps2_command+0x4f/0xc0 [psmouse] [ 6.512734] elantech_change_report_id+0x1e6/0x256 [psmouse] [ 6.512799] ? elantech_report_trackpoint.constprop.0.cold+0xd/0xd [psmouse] [ 6.512863] ? ps2_command+0x7f/0x90 [ 6.512877] elantech_query_info.cold+0x6bd/0x9ed [psmouse] [ 6.512943] ? elantech_setup_ps2+0x460/0x460 [psmouse] [ 6.513005] ? psmouse_reset+0x69/0xb0 [psmouse] [ 6.513064] ? psmouse_attr_set_helper+0x2a0/0x2a0 [psmouse] [ 6.513122] ? phys_pmd_init+0x30e/0x521 [ 6.513137] elantech_init+0x8a/0x200 [psmouse] [ 6.513200] ? elantech_init_ps2+0xf0/0xf0 [psmouse] [ 6.513249] ? elantech_query_info+0x440/0x440 [psmouse] [ 6.513296] ? synaptics_send_cmd+0x60/0x60 [psmouse] [ 6.513342] ? elantech_query_info+0x440/0x440 [psmouse] [ 6.513388] ? psmouse_try_protocol+0x11e/0x170 [psmouse] [ 6.513432] psmouse_extensions+0x65d/0x6e0 [psmouse] [ 6.513476] ? psmouse_try_protocol+0x170/0x170 [psmouse] [ 6.513519] ? mutex_unlock+0x22/0x40 [ 6.513526] ? ps2_command+0x7f/0x90 [ 6.513536] ? psmouse_probe+0xa3/0xf0 [psmouse] [ 6.513580] psmouse_switch_protocol+0x27d/0x2e0 [psmouse] [ 6.513624] psmouse_connect+0x272/0x530 [psmouse] [ 6.513669] serio_driver_probe+0x55/0x70 [ 6.513679] really_probe+0x190/0x720 [ 6.513689] driver_probe_device+0x160/0x1f0 [ 6.513697] device_driver_attach+0x119/0x130 [ 6.513705] ? device_driver_attach+0x130/0x130 [ 6.513713] __driver_attach+0xe7/0x1a0 [ 6.513720] ? device_driver_attach+0x130/0x130 [ 6.513728] bus_for_each_dev+0xfb/0x150 [ 6.513738] ? subsys_dev_iter_exit+0x10/0x10 [ 6.513748] ? _raw_write_unlock_bh+0x30/0x30 [ 6.513757] driver_attach+0x2d/0x40 [ 6.513764] serio_handle_event+0x199/0x3d0 [ 6.513775] process_one_work+0x471/0x740 [ 6.513785] worker_thread+0x2d2/0x790 [ 6.513794] ? process_one_work+0x740/0x740 [ 6.513802] kthread+0x1b4/0x1e0 [ 6.513809] ? set_kthread_struct+0x80/0x80 [ 6.513816] ret_from_fork+0x22/0x30

[ 6.513832] The buggy address belongs to the page: [ 6.513838] page:00000000bc35e189 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1024d7 [ 6.513847] flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff) [ 6.513860] raw: 0 ---truncated---

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.4%
EPSS %ILE
34th
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

March 4, 2024

Last Modified

February 14, 2025

References (4)

Vendor Advisories for CVE-2021-47097(4)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-trustyai-service-rhel8:v2.13.1-12024-10-24redhat
redhatrhoai/odh-trustyai-service-rhel8:v2.14.0-402024-10-17redhat
redhatkernel-rt-0:4.18.0-553.22.1.rt7.363.el8_102024-09-24redhat
redhatkernel-0:4.18.0-553.22.1.el8_102024-09-24redhat

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.46-4 ... 5.10.92-1~bpo10+1 (6 versions)
  • every version up to 5.10.92-1: fixed in 5.10.92-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 232 rows on record for this CVE, as 97 entries (3 repeats merged).

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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-47097?
CVE-2021-47097 is a high-severity vulnerability; its CVE record was published on March 4, 2024. In the Linux kernel, the following vulnerability has been resolved: Input: elantech - fix stack out of bound access in elantech_change_report_id() The array param[] in elantech_change_report_id() must be at least 3 bytes, because elantech_read_reg_params() is calling ps2_command() with…
When was the CVE record for CVE-2021-47097 published?
The CVE record for CVE-2021-47097 was published on March 4, 2024. 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 February 14, 2025; the record at its source may have been updated since.
Is CVE-2021-47097 actively exploited?
CVE-2021-47097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-47097?
CVE-2021-47097 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2021-47097?
A fix for CVE-2021-47097 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-47097 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-2021-47097

Explore →

Is Your Infrastructure Affected by CVE-2021-47097?

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

Book a Demo →Browse All CVEs