Skip to content
Threat Brief

← All advisories

CVE-2026-80931

High 7.8No known exploitationFix available

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

Record last updated

CVSS score

7.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.1%

Higher than 3% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before 6df05f630c84a109736642362e452089886f99746df05f630c84a109736642362e452089886f9974CVE Program
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before 169ae5e65e5aaf213b6a578f6478a9fd2e523606169ae5e65e5aaf213b6a578f6478a9fd2e523606CVE Program
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before b30c021c6073559ea6851b522d8a17a524a27b4ab30c021c6073559ea6851b522d8a17a524a27b4aCVE Program
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before 1d08877fc37e90945df38d255715bd1d6c052d461d08877fc37e90945df38d255715bd1d6c052d46CVE Program
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before bf76d61e118b7044600a65775a3bf8adc2c6823dbf76d61e118b7044600a65775a3bf8adc2c6823dCVE Program
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before 0f6496b34cc2919420f303b2aabdd9f71e084b560f6496b34cc2919420f303b2aabdd9f71e084b56CVE Program
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before cb55c5da9828f77db2a2701316949d4de1e9b773cb55c5da9828f77db2a2701316949d4de1e9b773CVE Program
LinuxLinuxfrom ebc4768ac4971eab4b570e733e47ac9dfd0e4175 before ae0c79a8527044e54d81fd5a3b49ce6177633758ae0c79a8527044e54d81fd5a3b49ce6177633758CVE Program
LinuxLinux4.15Not documentedCVE Program
Microsoftazl3 kernel 6.6.150.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.152.1-1 on Azure Linux 3.0Not documented6.6.157.1-1Microsoft MSRC
LinuxLinux (unaffected)from 5.10.270 up to and including 5.10.*Not documentedCVE Program
LinuxLinux (unaffected)from 5.15.221 up to and including 5.15.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.1.188 up to and including 6.1.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.109 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.50 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.157 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.4 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.15Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references