CVE-2022-48806

In the Linux kernel, the following vulnerability has been resolved:

eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX

Commit effa453168a7 (i2c: i801: Dont 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.

Weakness

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Affected Software

Potential Mitigations

• Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
• If possible, choose a language or compiler that performs automatic bounds checking.
• Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
• Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
• Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
• Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
• Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
• Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
• Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/92.html

References

• https://git.kernel.org/stable/c/3937c35493ee2847aaefcfa5460e94b7443eef49
• https://git.kernel.org/stable/c/9443ddeb3754e9e382a396b50adc1961301713ce
• https://git.kernel.org/stable/c/9a5f471ae380f9fcb9756d453c12ca1f8595a93c
• https://git.kernel.org/stable/c/a37960df7eac3cc8094bd1ab84864e9e32c91345
• https://git.kernel.org/stable/c/c0689e46be23160d925dca95dfc411f1a0462708
• https://git.kernel.org/stable/c/3937c35493ee2847aaefcfa5460e94b7443eef49
• https://git.kernel.org/stable/c/9443ddeb3754e9e382a396b50adc1961301713ce
• https://git.kernel.org/stable/c/9a5f471ae380f9fcb9756d453c12ca1f8595a93c
• https://git.kernel.org/stable/c/a37960df7eac3cc8094bd1ab84864e9e32c91345
• https://git.kernel.org/stable/c/c0689e46be23160d925dca95dfc411f1a0462708