CVE-2026-43047

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

HID: multitouch: Check to ensure report responses match the request

It is possible for a malicious (or clumsy) device to respond to a specific report's feature request using a completely different report ID. This can cause confusion in the HID core resulting in nasty side-effects such as OOB writes.

Add a check to ensure that the report ID in the response, matches the one that was requested. If it doesn't, omit reporting the raw event and return early.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.2%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 8, 2026

Advisory Details (8)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e716edafedad4952fe3a4a273d2e039a84e8681a
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c7a27bb4d0f6573ca0f9c7ef0b63291486239190
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a61163daf8a90b4a7ef154d5fc9c525f665734e3
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f66fdbc077faed3b52519228d21d81979e92249
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74c6015375d8b9bc1b1eb79f20636c8e894bcad7
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a4acd3e86fe5584050c213d95147eba33856033
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/516da3f25cfe18643835af1cf09b0e9ffc36c383
generic

HID: multitouch: Check to ensure report responses match the request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2edc92f89eee328b5be5706b5d431bf90669e9c0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 111 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-43047?
CVE-2026-43047 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: multitouch: Check to ensure report responses match the request It is possible for a malicious (or clumsy) device to respond to a specific report's feature request using a completely different report ID. This can cause…
When was CVE-2026-43047 disclosed?
CVE-2026-43047 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43047 actively exploited?
CVE-2026-43047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43047?
CVE-2026-43047 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43047?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43047, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43047

Explore →

Is Your Infrastructure Affected by CVE-2026-43047?

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

Start Free Scan →Browse All CVEs