{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-23178 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23178 is a high-severity memory corruption vulnerability in Linux, published on 14 Feb 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-23178 and fix it if it is affected.\n\nWhat it is: CVE-2026-23178 is a high-severity memory corruption vulnerability in Linux, published on 14 Feb 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-23178 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-23178/ (Markdown: https://insights.sbomify.com/CVE-2026-23178/index.md)","id":"CVE-2026-23178","markdown":"https://insights.sbomify.com/CVE-2026-23178/index.md","name":"CVE-2026-23178","record":{"aliases":["BELL-CVE-2026-23178","DEBIAN-CVE-2026-23178","GHSA-rhhh-mwpc-m2qj","ROOT-OS-DEBIAN-12-CVE-2026-23178","ROOT-OS-DEBIAN-13-CVE-2026-23178","ROOT-OS-UBUNTU-2204-CVE-2026-23178","ROOT-OS-UBUNTU-2404-CVE-2026-23178","UBUNTU-CVE-2026-23178"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel HID driver","requires_auth":"low_privilege","summary":"A buffer overflow in the Linux kernel's i2c-hid driver allows potential code execution or privilege escalation, though exploitation requires root access to hidraw devices.","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":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nHID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report()\n\n`i2c_hid_xfer` is used to read `recv_len + sizeof(__le16)` bytes of data\ninto `ihid-\u003erawbuf`.\n\nThe former can come from the userspace in the hidraw driver and is only\nbounded by HID_MAX_BUFFER_SIZE(16384) by default (unless we also set\n`max_buffer_size` field of `struct hid_ll_driver` which we do not).\n\nThe latter has size determined at runtime by the maximum size of\ndifferent report types you could receive on any particular device and\ncan be a much smaller value.\n\nFix this by truncating `recv_len` to `ihid-\u003ebufsize - sizeof(__le16)`.\n\nThe impact is low since access to hidraw devices requires root.","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":"HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report()","id":"CVE-2026-23178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()","id":"CVE-2026-23179"},"packages":[],"prev":{"headline":"mm, shmem: prevent infinite loop on truncate race","id":"CVE-2026-23177"},"products":["Linux"],"published":"2026-02-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A buffer overflow in the Linux kernel's i2c-hid driver allows potential code execution or privilege escalation, though exploitation requires root access to hidraw devices.","url":"https://insights.sbomify.com/CVE-2026-23178/"}