CVE-2026-31627

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
3.1%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (9)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd1650da24ed54c716aa9b69e9bbd8a662e492da
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fa00738ab30b07db1a43b9c85fc56b8cc3b7d197
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d87d5620125a03b1eadbd5df39748215d3db7ddb
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c0128c7157d639a931353ea344fb44aad6d6e17a
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aaaaec39ddbcd06770dca7f1adebc3b1242ebe7b
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f756a5964396da0fc9e0db33253a5b85dbbcbb6
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71b3c316b22c555d2769126a92b1244b15a9750d
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/377fae22a137b6b89f3f32399a58c52cf2325416
generic

i2c: s3c24xx: check the size of the SMBUS message before using it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d262da4bca6fab96e2e709feb95b31b0a9a03a7

Vendor Advisories for CVE-2026-31627(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 158 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 15:15 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
Show 75 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:53 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:49 UTCEPSS rescore
  14. 2026-06-14 23:40 UTCEG score recompute
  15. 2026-06-14 23:40 UTCVendor advisory
  16. 2026-06-14 23:40 UTCGHSA enrichment
  17. 2026-06-14 23:18 UTCEPSS rescore
  18. 2026-06-14 11:51 UTCEG score recompute
  19. 2026-06-14 11:51 UTCVendor advisory
  20. 2026-06-14 11:51 UTCGHSA enrichment
  21. 2026-06-13 23:00 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 01:46 UTCEG score recompute
  25. 2026-06-12 01:46 UTCVendor advisory
  26. 2026-06-12 01:46 UTCGHSA enrichment
  27. 2026-06-11 14:00 UTCEPSS rescore
  28. 2026-06-11 13:59 UTCEG score recompute
  29. 2026-06-11 13:59 UTCVendor advisory
  30. 2026-06-11 13:58 UTCGHSA enrichment
  31. 2026-06-10 22:18 UTCEPSS rescore
  32. 2026-06-10 13:22 UTCEPSS rescore
  33. 2026-06-10 12:05 UTCEG score recompute
  34. 2026-06-10 12:05 UTCVendor advisory
  35. 2026-06-10 12:05 UTCGHSA enrichment
  36. 2026-06-10 00:17 UTCEG score recompute
  37. 2026-06-10 00:17 UTCVendor advisory
  38. 2026-06-10 00:17 UTCGHSA enrichment
  39. 2026-06-09 12:30 UTCEG score recompute
  40. 2026-06-09 12:30 UTCVendor advisory
  41. 2026-06-09 12:30 UTCGHSA enrichment
  42. 2026-06-09 00:43 UTCEG score recompute
  43. 2026-06-09 00:43 UTCVendor advisory
  44. 2026-06-09 00:43 UTCGHSA enrichment
  45. 2026-06-08 14:17 UTCEPSS rescore
  46. 2026-06-08 14:17 UTCEPSS rescore
  47. 2026-06-08 04:45 UTCEG score recompute
  48. 2026-06-08 04:45 UTCVendor advisory
  49. 2026-06-08 04:45 UTCGHSA enrichment
  50. 2026-06-07 16:58 UTCEG score recompute
  51. 2026-06-07 16:58 UTCVendor advisory
  52. 2026-06-07 16:58 UTCGHSA enrichment
  53. 2026-06-07 15:25 UTCEPSS rescore
  54. 2026-06-07 15:25 UTCEPSS rescore
  55. 2026-06-07 15:25 UTCEPSS rescore
  56. 2026-06-07 05:10 UTCEG score recompute
  57. 2026-06-07 05:10 UTCVendor advisory
  58. 2026-06-07 05:10 UTCGHSA enrichment
  59. 2026-06-06 17:23 UTCEG score recompute
  60. 2026-06-06 17:23 UTCVendor advisory
  61. 2026-06-06 17:23 UTCGHSA enrichment
  62. 2026-06-06 13:47 UTCEPSS rescore
  63. 2026-06-06 13:47 UTCEPSS rescore
  64. 2026-06-06 04:18 UTCEG score recompute
  65. 2026-06-06 04:18 UTCVendor advisory
  66. 2026-06-06 04:18 UTCGHSA enrichment
  67. 2026-06-05 22:47 UTCEPSS rescore
  68. 2026-06-05 22:47 UTCEPSS rescore
  69. 2026-06-05 15:10 UTCEG score recompute
  70. 2026-06-05 15:10 UTCVendor advisory
  71. 2026-06-05 15:10 UTCGHSA enrichment
  72. 2026-06-05 06:10 UTCEPSS rescore
  73. 2026-06-05 06:10 UTCEPSS rescore
  74. 2026-06-05 02:45 UTCEG score recompute
  75. 2026-06-05 02:45 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-31627?
CVE-2026-31627 is a high vulnerability published on April 24, 2026. 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..I2CSMBUSBLOCK_MAX before processing it. This is…
When was CVE-2026-31627 disclosed?
CVE-2026-31627 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31627 actively exploited?
CVE-2026-31627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31627?
CVE-2026-31627 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31627, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-31627

Explore →

Is Your Infrastructure Affected by CVE-2026-31627?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs