CVE-2026-43048

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.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: core: Mitigate potential OOB by removing bogus memset()

The memset() in hid_report_raw_event() has the good intention of clearing out bogus data by zeroing the area from the end of the incoming data string to the assumed end of the buffer. However, as we have previously seen, doing so can easily result in OOB reads and writes in the subsequent thread of execution.

The current suggestion from one of the HID maintainers is to remove the memset() and simply return if the incoming event buffer size is not large enough to fill the associated report.

Suggested-by Benjamin Tissoires

[bentiss: changed the return value]

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
15.1%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (3)

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

HID: core: Mitigate potential OOB by removing bogus memset() - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: core: Mitigate potential OOB by removing bogus memset() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f71034649738fdeb6859b8d6cddf132024fac06
generic

HID: core: Mitigate potential OOB by removing bogus memset() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a3fe972a7cb1404f693d6f1711f32bc1d244b1c

Vendor Advisories for CVE-2026-43048(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× 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 123 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43048?
CVE-2026-43048 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: core: Mitigate potential OOB by removing bogus memset() The memset() in hidreportraw_event() has the good intention of clearing out bogus data by zeroing the area from the end of the incoming data string to the assumed end of…
When was CVE-2026-43048 disclosed?
CVE-2026-43048 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43048 actively exploited?
CVE-2026-43048 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43048?
CVE-2026-43048 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-43048?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43048, 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-43048

Explore →

Is Your Infrastructure Affected by CVE-2026-43048?

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