CVE-2022-48806

eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX

MEDIUM

5.5

CVSS Score

Published: July 16, 2024 at 11:43 AM UTC

Updated: June 17, 2026 at 05:16 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 4.14.263v ≥ 4.19.226v ≥ 4.4.300v ≥ 4.9.2984.14.263 ≤ v < 4.154.19.226 ≤ v < 4.204.4.300 ≤ v < 4.54.9.298 ≤ v < 4.105.10.94 ≤ v < 5.10.1015.15.17 ≤ v < 5.15.245.16.3 ≤ v < 5.16.105.4.174 ≤ v < 5.4.180202d0e22fe512df0f1cb6253d40ce1058e37324725714ad6bf5e98025579fa4c08ff2041a663910c4.14.263 4.19.226 4.4.300 4.9.298 5.10.94 5.15.17 5.16.3 5.17 rc1 5.17 rc2 5.17 rc3 5.4.1747414af7bdad9a9cddb3a765ca98ea207048618c574650c34f93044d3ab441235f161f9e1e761e96b7d9beb6e3c2e852e884113d6803ea4b3643ae38a126a8c3dd51519513141b4fc94fd4813bca2c0faca56c298e2a6d20ab6308e203a8d37f2a7759d3be9313f755a7bfa02230b15731d07074d5255ecbeffa453168a7eeb8a562ff4edc1dbf9067360a61

Vendor states this is fixed in 3937c35493ee2847aaefcfa5460e94b7443eef49 (fixed)

Vendor states this is fixed in 9443ddeb3754e9e382a396b50adc1961301713ce (fixed)

Vendor states this is fixed in 9a5f471ae380f9fcb9756d453c12ca1f8595a93c (fixed)

Vendor states this is fixed in a37960df7eac3cc8094bd1ab84864e9e32c91345 (fixed)

Vendor states this is fixed in c0689e46be23160d925dca95dfc411f1a0462708 (fixed)

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.10.101, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.15.24, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.16.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.180, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references