CVE-2026-23178

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report()

i2c_hid_xfer is used to read recv_len + sizeof(__le16) bytes of data into ihid->rawbuf.

The former can come from the userspace in the hidraw driver and is only bounded by HID_MAX_BUFFER_SIZE(16384) by default (unless we also set max_buffer_size field of struct hid_ll_driver which we do not).

The latter has size determined at runtime by the maximum size of different report types you could receive on any particular device and can be a much smaller value.

Fix this by truncating recv_len to ihid->bufsize - sizeof(__le16).

The impact is low since access to hidraw devices requires root.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

February 14, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/786ec171788bdf9dda38789163f1b1fbb47f2d1e
generic

HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2497ff38c530b1af0df5130ca9f5ab22c5e92f29
generic

HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2124279f1f8c32c1646ce98e75a1a39b23b7db76

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-12ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-12ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-12ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-12ubuntu
linuxKernel @ 6.1.163—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.

All Vendor Advisories

(7)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2026-23178?
CVE-2026-23178 is a high vulnerability published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid: fix potential buffer overflow in i2chidget_report() i2chidxfer is used to read recvlen + sizeof(_le16) bytes of data into ihid->rawbuf. The former can come from the userspace in the hidraw driver and is only bounded…
When was CVE-2026-23178 disclosed?
CVE-2026-23178 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23178 actively exploited?
CVE-2026-23178 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 96.0% of all scored CVEs.
What is the CVSS score of CVE-2026-23178?
CVE-2026-23178 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23178, 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-23178

Explore →

Is Your Infrastructure Affected by CVE-2026-23178?

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

Start Free Scan →Browse All CVEs