LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48806: eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX

In the Linux kernel, the following vulnerability has been resolved: eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX Commit effa453168a7 ("i2c: i801: Don't silently correct invalid transfer size") revealed that ee1004_eeprom_read() did not properly limit how many bytes to read at once. In particular, i2c_smbus_read_i2c_block_data_or_emulated() takes the length to read as an u8. If count == 256 after taking into account the offset and page boundary, the cast to u8 overflows. And this is common when user space tries to read the entire EEPROM at once. To fix it, limit each read to I2C_SMBUS_BLOCK_MAX (32) bytes, already the maximum length i2c_smbus_read_i2c_block_data_or_emulated() allows.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-48806 is a Linux kernel flaw in the ee1004 EEPROM driver. A read request for a full EEPROM could exceed the allowed I2C SMBus block size because a 256-byte length overflows an 8-bit value. Public sources do not provide a CVSS score, impact rating, or evidence of active exploitation.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency, unless your environment exposes EEPROM reads to untrusted local users. Schedule validation during normal Linux patch governance and confirm vendor coverage.

Technical view

ee1004_eeprom_read() failed to cap per-read length before calling i2c_smbus_read_i2c_block_data_or_emulated(), whose length parameter is u8. When count becomes 256 after offset and page-boundary handling, the cast overflows. The kernel fix limits each read to I2C_SMBUS_BLOCK_MAX, 32 bytes.

Likely exposure

Exposure is limited to Linux systems using the ee1004 EEPROM driver and code paths where userspace reads EEPROM data. Exact affected release ranges are not fully clear from the provided record; confirm against kernel or distribution backports.

Exploitation context

The source describes a userspace-triggered read-size handling bug, commonly hit when reading an entire EEPROM at once. No cited source or KEV entry indicates active exploitation, public weaponization, or remote exploitation.

Researcher notes

The public record lacks CVSS, CWE, and explicit impact details. Analysis should focus on the ee1004 driver fix: bounding SMBus block reads to 32 bytes to prevent u8 length overflow at 256-byte reads.

Mitigation direction

  • Apply Linux kernel updates containing the ee1004 read-length limit fix.
  • Check distribution advisories for CVE-2022-48806 backports.
  • Prioritize systems where untrusted local users can access EEPROM read interfaces.
  • If uncertain, request vendor confirmation for your kernel build.

Validation and detection

  • Confirm the running kernel includes the referenced stable fix or vendor backport.
  • Review kernel package changelogs for CVE-2022-48806 or the ee1004 fix text.
  • Inventory systems with the ee1004 driver built or loaded.
  • Document any systems requiring vendor clarification due to custom kernels.
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-2022-48806 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
6Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaca56c298e2a6d20ab6308e203a8d37f2a7759d3, 25714ad6bf5e98025579fa4c08ff2041a663910c, be9313f755a7bfa02230b15731d07074d5255ecb, 07d9beb6e3c2e852e884113d6803ea4b3643ae38, effa453168a7eeb8a562ff4edc1dbf9067360a61, 74650c34f93044d3ab441235f161f9e1e761e96b, a126a8c3dd51519513141b4fc94fd4813bca2c0f, 202d0e22fe512df0f1cb6253d40ce1058e373247, 7414af7bdad9a9cddb3a765ca98ea207048618c5unaffected
LinuxLinux5.4.174, 5.10.94, 5.15.17, 5.16.3unaffected
Weakness

CWE details

No CWE listed

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