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

A local Linux kernel flaw could let an oversized HID report overwrite memory, potentially crashing the system or altering protected data. Although the supplied CVSS score is 7.8, the kernel description calls the practical impact low because accessing the relevant hidraw device requires root. This is not presented as a remote vulnerability.

Executive priority

Patch during the next appropriate kernel maintenance window, prioritizing shared or sensitive systems using I2C HID devices. The memory-corruption consequences are serious, but the stated root-access prerequisite and absence of known exploitation do not support an emergency internet-wide response.

Technical view

i2c_hid_get_report() could accept a userspace-controlled receive length larger than the runtime-sized raw buffer. i2c_hid_xfer() then reads that length plus a two-byte field into the buffer, creating a potential overflow. The stable fixes cap the receive length at the buffer size minus those two bytes.

Likely exposure

Exposure is limited to Linux systems using the I2C HID and hidraw path. The supplied record identifies affected Linux releases across several maintained branches, but distributions may backport fixes without changing major version numbers. The source states that hidraw access requires root, substantially reducing ordinary-user exposure.

Exploitation context

The issue requires local access and interaction with a hidraw device. The supplied source says this access requires root, while the CVSS vector records low privileges; that discrepancy should be checked against distribution permissions. The CVE is not listed as KEV, and the bundle provides no evidence of active exploitation or a public exploit.

Researcher notes

The important boundary is between userspace-controlled recv_len, the additional sizeof(__le16) read, and the device-dependent ihid->rawbuf size. The fix truncates recv_len to ihid->bufsize minus that field. Researchers should verify actual hidraw permissions and vendor backports rather than relying solely on version strings.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable cited stable fix.
  • Use distribution advisories or changelogs to identify backported fixes accurately.
  • Until updated, keep hidraw device access restricted to trusted privileged users.
  • Prioritize systems where local privileged processes interact with I2C HID devices.

Validation and detection

  • Inventory running kernel builds and identify systems using I2C HID devices.
  • Check vendor advisories for CVE-2026-23178 or the cited stable commits.
  • Review hidraw device permissions and identify processes permitted to access them.
  • After updating, verify the fixed kernel is running and test attached HID devices.
Prepared
Confidence
medium
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.