{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89628 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89628 is a 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-89628 and fix it if it is affected.\n\nWhat it is: CVE-2026-89628 is a 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-89628 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-89628/ (Markdown: https://insights.sbomify.com/CVE-2026-89628/index.md)","id":"CVE-2026-89628","markdown":"https://insights.sbomify.com/CVE-2026-89628/index.md","name":"CVE-2026-89628","record":{"aliases":["AZL-100241","BELL-CVE-2026-89628","DEBIAN-CVE-2026-89628","GHSA-84x9-cxq8-hpgq","UBUNTU-CVE-2026-89628"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A local attacker with root privileges can read adjacent kernel memory via a crafted HID device response in the picolcd driver.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nHID: picolcd: clamp eeprom debugfs read to bytes actually received\n\npicolcd_debug_eeprom_read() trusts resp-\u003eraw_data[2] -- a length byte\nsupplied by the device in its REPORT_EE_DATA reply -- clamped only to\nthe caller's read() count:\n\n\tret = resp-\u003eraw_data[2];\n\tif (ret \u003e s)\n\t\tret = s;\n\tif (copy_to_user(u, resp-\u003eraw_data+3, ret))\n\nIt never checks resp-\u003eraw_size, the number of bytes picolcd_raw_event()\nactually copied into the 64-byte raw_data[] of the kmalloc'd struct\npicolcd_pending. A device (or a spoofed picoLCD) returning a length byte\nof 0xff, read with a count \u003e= 255, makes copy_to_user() read past\nraw_data[] into adjacent slab memory and return it to userspace through\nthe debugfs \"eeprom\" file:\n\n\tBUG: KASAN: slab-out-of-bounds in _copy_to_user\n\tRead of size 255 ... picolcd_debug_eeprom_read+0x214/0x2f0 [hid_picolcd]\n\nThe debug-dump path in the same file already validates the device length\nbyte against the received size before trusting it; this read does not.\nThe file is created S_IRUSR (root-only) and a crafted device is needed,\nso it is neither unprivileged- nor remotely-triggerable.\n\nClamp the copy length to resp-\u003eraw_size - 3 (the payload actually\nreceived, minus the 3-byte header), floored at 0 for short replies.","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: picolcd: clamp eeprom debugfs read to bytes actually received","id":"CVE-2026-89628","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"HID: corsair-void: Check size of status and firmware events before reading them","id":"CVE-2026-89629"},"packages":[],"prev":{"headline":"HID: roccat: free buffered reports when destroying device","id":"CVE-2026-89627"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker with root privileges can read adjacent kernel memory via a crafted HID device response in the picolcd driver.","url":"https://insights.sbomify.com/CVE-2026-89628/"}