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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 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)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

May 1, 2026

Last Modified

August 5, 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.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.22—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 rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.12-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 85.0% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs