LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-23178 is a Linux kernel buffer overflow in the i2c-hid driver. A report length from userspace could exceed the driver buffer size. The source says impact is low because hidraw device access requires root, but the CVSS score is high because kernel memory corruption can affect confidentiality, integrity, and availability.

Executive priority

Treat this as a normal but timely kernel maintenance item, not an emergency based on the supplied evidence. Prioritize systems where local root access is shared, delegated, or harder to control, and align remediation with vendor kernel updates.

Technical view

In i2c_hid_get_report(), i2c_hid_xfer could read recv_len plus a length field into ihid->rawbuf. recv_len may come from hidraw userspace and is bounded by HID_MAX_BUFFER_SIZE, while the actual i2c-hid buffer may be smaller. The fix truncates recv_len to ihid->bufsize minus sizeof(__le16).

Likely exposure

Exposure is limited to Linux systems running affected kernels with i2c-hid and hidraw paths available. The source bundle lists Linux as affected and provides stable kernel commits. Distro-specific package status is not provided, so teams must map their kernel builds to vendor advisories or upstream commits.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. The vulnerable path is local through hidraw userspace interaction. The source explicitly notes low impact because hidraw access requires root, although the CVSS vector rates local exploitation with high impact.

Researcher notes

The key evidence is upstream Linux stable commit text describing a bounds mismatch between hidraw recv_len and ihid->rawbuf size. The source bundle does not provide CWE mapping, proof of exploitation, or distribution-level fixed package versions.

Mitigation direction

  • Update to a kernel version containing the referenced stable fix commits.
  • Check your Linux distribution advisory for packaged kernel backports.
  • Prioritize laptops, embedded devices, and hosts using i2c-hid peripherals.
  • Restrict unnecessary local administrative access to systems until patched.
  • Monitor kernel logs for HID or i2c-hid instability during remediation.

Validation and detection

  • Inventory kernel versions and compare them with vendor advisories or upstream stable commits.
  • Identify systems exposing i2c-hid and hidraw device paths.
  • Confirm patched kernels include the recv_len truncation fix.
  • Verify no unsupported custom kernels remain in production.
  • Document exceptions where vendor patch status is still unknown.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23178 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-23178Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux85df713377ddc0482071c3e6b64c37bd1e48f1f1, 85df713377ddc0482071c3e6b64c37bd1e48f1f1, 85df713377ddc0482071c3e6b64c37bd1e48f1f1, 85df713377ddc0482071c3e6b64c37bd1e48f1f1, 85df713377ddc0482071c3e6b64c37bd1e48f1f1unaffected
LinuxLinux5.18, 0, 6.1.163, 6.6.124, 6.12.70, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.