{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80931 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80931 is a high-severity memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80931 and fix it if it is affected.\n\nWhat it is: CVE-2026-80931 is a high-severity memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80931 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80931/ (Markdown: https://insights.sbomify.com/CVE-2026-80931/index.md)","id":"CVE-2026-80931","markdown":"https://insights.sbomify.com/CVE-2026-80931/index.md","name":"CVE-2026-80931","record":{"aliases":["AZL-100286","BELL-CVE-2026-80931","DEBIAN-CVE-2026-80931","GHSA-3cwq-59j3-h9hj","UBUNTU-CVE-2026-80931"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A buffer overflow in the Linux kernel DS28E17 driver allows out-of-bounds writes via malicious I2C responses, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nw1: ds28e17: reject an oversize length on an I2C block read\n\nw1_f19_i2c_master_transfer() is the master_xfer for the DS28E17 1-Wire\nto I2C bridge. On an I2C_M_RECV_LEN read, it takes the length from the\ndevice. The downstream slave puts a length byte in buf[0]. The driver\nthen reads that many bytes into buf[1] with w1_f19_i2c_read().\n\nbuf[0] is controlled by the device and can be 0 to 255.\nw1_f19_i2c_read() only rejects a zero count. The caller buffer is\nI2C_SMBUS_BLOCK_MAX + 2, so 34 bytes. A length above 32 makes the read\nrun past it, up to about 222 bytes out of bounds.\n\nThe SMBus core does check buf[0] against I2C_SMBUS_BLOCK_MAX. That\ncheck runs after master_xfer returns. By then the write is already\ndone. i2c-algo-bit rejects an oversize length before it copies, and\nreturns -EPROTO.\n\nReject a length above I2C_SMBUS_BLOCK_MAX at both RECV_LEN sites, the\nsame way i2c-algo-bit does.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"w1: ds28e17: reject an oversize length on an I2C block read","id":"CVE-2026-80931","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"vsock/virtio: flush works in dependency order","id":"CVE-2026-80932"},"packages":[],"prev":{"headline":"tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout","id":"CVE-2026-80930"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A buffer overflow in the Linux kernel DS28E17 driver allows out-of-bounds writes via malicious I2C responses, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-80931/"}