Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-48806, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected aca56c298e2a6d20ab6308e203a8d37f2a7759d3 – < 3937c35493ee2847aaefcfa5460e94b7443eef49
    • affected 25714ad6bf5e98025579fa4c08ff2041a663910c – < a37960df7eac3cc8094bd1ab84864e9e32c91345
    • affected be9313f755a7bfa02230b15731d07074d5255ecb – < 9a5f471ae380f9fcb9756d453c12ca1f8595a93c
    • affected 07d9beb6e3c2e852e884113d6803ea4b3643ae38 – < 9443ddeb3754e9e382a396b50adc1961301713ce
    • affected effa453168a7eeb8a562ff4edc1dbf9067360a61 – < c0689e46be23160d925dca95dfc411f1a0462708
    • affected 74650c34f93044d3ab441235f161f9e1e761e96b
    • affected a126a8c3dd51519513141b4fc94fd4813bca2c0f
    • affected 202d0e22fe512df0f1cb6253d40ce1058e373247
    • affected 7414af7bdad9a9cddb3a765ca98ea207048618c5
    • affected 4.4.300 – < 4.5
    • affected 4.9.298 – < 4.10
    • affected 4.14.263 – < 4.15
    • affected 4.19.226 – < 4.20
  • Linux · Linux

    • affected 5.4.174 – < 5.4.180
    • affected 5.10.94 – < 5.10.101
    • affected 5.15.17 – < 5.15.24
    • affected 5.16.3 – < 5.16.10

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-48806 badge
[![CVE-2022-48806](https://cveledger.app/badge/CVE-2022-48806.svg)](https://cveledger.app/cve/CVE-2022-48806)

Record last updated .