CVE-2026-46001: hwmon: (pt5161l) Fix bugs in pt5161l_read_block_data()

Published May 27, 2026
·
Updated

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

hwmon: (pt5161l) Fix bugs in pt5161lreadblockdata()

Fix two bugs in pt5161lreadblockdata():

1. Buffer overrun: The local buffer rbuf is declared as u8 rbuf[24], but i2csmbusreadblockdata() can return up to I2CSMBUSBLOCKMAX (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 I2CSMBUSBLOCKMAX.

2. Unexpected positive return on length mismatch: When all three retries are exhausted because the device returns data with an unexpected length, i2csmbusreadblockdata() 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.

Affected Software

4 affected components
The Linux Foundation Linux Kernel
Linux Linux kernel>=6.9<6.12.86
Linux Linux kernel>=6.13<6.18.27
Linux Linux kernel>=6.19<7.0.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Operational

    Apply the Linux kernel fix for hwmon (pt5161l) that corrects pt5161l_read_block_data(): resize the local buffer rbuf to I2C_SMBUS_BLOCK_MAX to prevent buffer overruns, and return -EIO when retries are exhausted with a positive byte count. Obtain and apply the upstream kernel patch or update your kernel to a release containing this fix, then rebuild and deploy the patched kernel.

Event History

May 27, 2026
CVE Published
via MITRE·12:55 PM
Data Sourced
via MITRE·12:55 PM
Description
Data Sourced
via NVD·02:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-46001?

CVE-2026-46001 has a high severity rating of 7.8 according to CVSS 3.1.

2

How do I fix CVE-2026-46001?

To fix CVE-2026-46001, update your Linux kernel to the latest version where the vulnerability has been patched.

3

What type of vulnerability is CVE-2026-46001?

CVE-2026-46001 is classified as a buffer overflow vulnerability.

4

Which software is affected by CVE-2026-46001?

CVE-2026-46001 affects the Linux kernel developed by The Linux Foundation.

5

What are the consequences of exploiting CVE-2026-46001?

Exploiting CVE-2026-46001 could lead to unauthorized access and manipulation of kernel memory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203