CVE-2026-46001

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data()

Fix two bugs in pt5161l_read_block_data():

  • Buffer overrun: The local buffer rbuf is declared as u8 rbuf[24],
but i2c_smbus_read_block_data() can return up to I2C_SMBUS_BLOCK_MAX (32) bytes. The i2c-core copies the data into the caller's buffer before the return value can be checked, so the post-read length validation does not prevent a stack overrun if a device returns more than 24 bytes. Resize the buffer to I2C_SMBUS_BLOCK_MAX.
  • Unexpected positive return on length mismatch: When all three
retries are exhausted because the device returns data with an unexpected length, i2c_smbus_read_block_data() returns a positive byte count. The function returns this directly, and callers treat any non-negative return as success, processing stale or incomplete buffer contents. Return -EIO when retries are exhausted with a positive return value, preserving the negative error code on I2C failure.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (4)

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

hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95d48e37a1304d6148406c799479c0fb505aefa7
generic

hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7eccabff1c9ec15e4b6fe186d5c147b13a9cdb4e
generic

hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24c73e93d6a756e1b8626bb259d2e07c5b89b370

Vendor Advisories for CVE-2026-46001(1)

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

Patch Availability(6)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 17× in last 7d / 43× 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 119 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46001?
CVE-2026-46001 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: (pt5161l) Fix bugs in pt5161lreadblock_data() Fix two bugs in pt5161lreadblock_data(): 1. Buffer overrun: The local buffer rbuf is declared as u8 rbuf[24], but i2csmbusreadblockdata() can return up to I2CSMBUSBLOCK_MAX (32)…
When was CVE-2026-46001 disclosed?
CVE-2026-46001 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46001 actively exploited?
CVE-2026-46001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-46001?
CVE-2026-46001 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46001?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46001, 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-46001

Explore →

Is Your Infrastructure Affected by CVE-2026-46001?

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