Linux Kernel up to 5.4.179/5.10.100/5.15.23/5.16.9 eeprom ee1004_eeprom_read information disclosure

Summaryinfo

A vulnerability described as problematic has been identified in Linux Kernel up to 5.4.179/5.10.100/5.15.23/5.16.9. Affected by this vulnerability is the function ee1004_eeprom_read of the component eeprom. Executing a manipulation can lead to information disclosure. This vulnerability is tracked as CVE-2022-48806. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 5.4.179/5.10.100/5.15.23/5.16.9. This vulnerability affects the function ee1004_eeprom_read of the component eeprom. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2022-48806 since 07/16/2024. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 5.4.180, 5.10.101, 5.15.24 or 5.16.10 eliminates this vulnerability. Applying the patch 3937c35493ee/a37960df7eac/9a5f471ae380/9443ddeb3754/c0689e46be23 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.0
• 5.1
• 5.2
• 5.3
• 5.4
• 5.4.179
• 5.5
• 5.6
• 5.7
• 5.8
• 5.9
• 5.10.100
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.16.0
• 5.16.1
• 5.16.2
• 5.16.3
• 5.16.4
• 5.16.5
• 5.16.6
• 5.16.7
• 5.16.8
• 5.16.9

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion