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 — 5 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(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-09-14ubuntu
linuxKernel @ 6.12.86—osv

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.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1—

Weakness Classification(1)

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

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 240 total refreshes for this CVE.

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

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.2% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs