CVE-2026-80931

w1: ds28e17: reject an oversize length on an I2C block read

HIGH
7.8
CVSS Score
Published: September 11, 2026 at 07:42 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: w1: ds28e17: reject an oversize length on an I2C block read w1_f19_i2c_master_transfer() is the master_xfer for the DS28E17 1-Wire to I2C bridge. On an I2C_M_RECV_LEN read, it takes the length from the device. The downstream slave puts a length byte in buf[0]. The driver then reads that many bytes into buf[1] with w1_f19_i2c_read(). buf[0] is controlled by the device and can be 0 to 255. w1_f19_i2c_read() only rejects a zero count. The caller buffer is I2C_SMBUS_BLOCK_MAX + 2, so 34 bytes. A length above 32 makes the read run past it, up to about 222 bytes out of bounds. The SMBus core does check buf[0] against I2C_SMBUS_BLOCK_MAX. That check runs after master_xfer returns. By then the write is already done. i2c-algo-bit rejects an oversize length before it copies, and returns -EPROTO. Reject a length above I2C_SMBUS_BLOCK_MAX at both RECV_LEN sites, the same way i2c-algo-bit does.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.15ebc4768ac4971eab4b570e733e47ac9dfd0e4175
Vendor states this is fixed in 0f6496b34cc2919420f303b2aabdd9f71e084b56 (fixed)
Vendor states this is fixed in 169ae5e65e5aaf213b6a578f6478a9fd2e523606 (fixed)
Vendor states this is fixed in 1d08877fc37e90945df38d255715bd1d6c052d46 (fixed)
Vendor states this is fixed in 6df05f630c84a109736642362e452089886f9974 (fixed)
Vendor states this is fixed in ae0c79a8527044e54d81fd5a3b49ce6177633758 (fixed)
Vendor states this is fixed in b30c021c6073559ea6851b522d8a17a524a27b4a (fixed)
Vendor states this is fixed in bf76d61e118b7044600a65775a3bf8adc2c6823d (fixed)
Vendor states this is fixed in cb55c5da9828f77db2a2701316949d4de1e9b773 (fixed)
Vendor states this is fixed in 4.15 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card