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-2026-31627i2c: s3c24xx: check the size of the SMBUS message before using it

Description

In the Linux kernel, the following vulnerability has been resolved: i2c: s3c24xx: check the size of the SMBUS message before using it The first byte of an i2c SMBUS message is the size, and it should be verified to ensure that it is in the range of 0..I2C_SMBUS_BLOCK_MAX before processing it. This is the same logic that was added in commit a6e04f05ce0b ("i2c: tegra: check msg length in SMBUS block read") to the i2c tegra driver.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 3 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-2026-31627, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (20 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < fd1650da24ed54c716aa9b69e9bbd8a662e492da
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < 8f756a5964396da0fc9e0db33253a5b85dbbcbb6
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < 2d262da4bca6fab96e2e709feb95b31b0a9a03a7
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < fa00738ab30b07db1a43b9c85fc56b8cc3b7d197
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < d87d5620125a03b1eadbd5df39748215d3db7ddb
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < 377fae22a137b6b89f3f32399a58c52cf2325416
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < 71b3c316b22c555d2769126a92b1244b15a9750d
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < aaaaec39ddbcd06770dca7f1adebc3b1242ebe7b
    • affected 85747311ecb6167c989093c64a13807366fdd3a9 – < c0128c7157d639a931353ea344fb44aad6d6e17a
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0.1 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .