In the Linux kernel, the following vulnerability has been resolved: hwmon: (pt5161l) Fix bugs in...

Description

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():

  1. 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.

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

Basic information

Type
unreviewed
Severity
high
Advisory on GitHub
Open advisory ↗
Repository advisory
Source code
Not specified
Published (advisory)
2026-05-27 15:33:20 UTC
Updated
2026-06-16 15:34:48 UTC
NVD published
2026-05-27

EPSS Score

Score Percentile
0.02% 6.85%

CVSS Scores

Base score Version Severity Vector
7.8 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.

Identifiers

CWEs

CWE id Name
CWE-787 Out-of-bounds Write

References

cvelogic Threat Intelligence