LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26593: i2c: i801: Fix block process call transactions

In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Fix block process call transactions According to the Intel datasheets, software must reset the block buffer index twice for block process call transactions: once before writing the outgoing data to the buffer, and once again before reading the incoming data from the buffer. The driver is currently missing the second reset, causing the wrong portion of the block buffer to be read.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26593 is a Linux kernel driver bug in the Intel i801 I2C/SMBus code. A buffer index is not reset a second time during a block process call, so the driver may read the wrong part of its buffer. The provided sources do not include CVSS, impact category, or active exploitation evidence.

Executive priority

Treat as a routine kernel maintenance item unless your environment depends heavily on affected Intel SMBus/I2C paths. There is no supplied evidence of active exploitation or critical severity, but kernel driver flaws still merit timely patching through normal update channels.

Technical view

The flaw is in Linux kernel i2c-i801 block process call handling. Intel documentation requires resetting the block buffer index before outgoing data is written and again before incoming data is read. The vulnerable driver missed the second reset, causing incorrect buffer reads. Kernel stable commits and Debian/Fedora advisories are cited as remediation sources.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds with the i2c-i801 driver path available or in use. The source bundle does not prove remote reachability, privilege requirements, or business impact, so exposure should be verified through kernel inventory and hardware or module usage.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not report active exploitation or public exploit availability. The available evidence describes a correctness flaw in kernel driver transaction handling, not a confirmed in-the-wild attack path.

Researcher notes

The key technical issue is the missing second block buffer index reset before reading returned data. The source bundle lacks CVSS, CWE, exploitability analysis, and precise operational impact. Review the upstream stable commits for exact code deltas and use distro advisories for package-level fixed versions.

Mitigation direction

  • Update Linux kernels using vendor packages containing the referenced stable fixes.
  • Apply Debian LTS or Fedora kernel advisories where those distributions are in use.
  • Prioritize systems using Intel i801 SMBus/I2C hardware or loading the i2c-i801 driver.
  • Check vendor guidance if running custom, embedded, or backported kernels.

Validation and detection

  • Inventory installed Linux kernel versions across affected fleets.
  • Confirm whether i2c-i801 is built, loadable, or active on relevant systems.
  • Map installed kernel packages against Debian, Fedora, or upstream stable fixed releases.
  • For custom kernels, verify inclusion of the linked stable commits.
  • Document systems where hardware exposure cannot be confirmed.
Prepared
Confidence
medium
Sources
11

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-2024-26593 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux315cd67c945351f8a569500f8ab16b7fa94026e8, 315cd67c945351f8a569500f8ab16b7fa94026e8, 315cd67c945351f8a569500f8ab16b7fa94026e8, 315cd67c945351f8a569500f8ab16b7fa94026e8, 315cd67c945351f8a569500f8ab16b7fa94026e8, 315cd67c945351f8a569500f8ab16b7fa94026e8, 315cd67c945351f8a569500f8ab16b7fa94026e8unaffected
LinuxLinux5.3, 0, 5.4.269, 5.10.210, 5.15.149, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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