{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90000 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90000 is a high-severity memory corruption vulnerability in Linux, published on 16 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-90000 and fix it if it is affected.\n\nWhat it is: CVE-2026-90000 is a high-severity memory corruption vulnerability in Linux, published on 16 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-90000 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-90000/ (Markdown: https://insights.sbomify.com/CVE-2026-90000/index.md)","id":"CVE-2026-90000","markdown":"https://insights.sbomify.com/CVE-2026-90000/index.md","name":"CVE-2026-90000","record":{"aliases":["AZL-101123","BELL-CVE-2026-90000","DEBIAN-CVE-2026-90000","GHSA-q6xg-4cv5-fxhc","UBUNTU-CVE-2026-90000"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel HID driver","requires_auth":"none","summary":"A malicious or undersized HID device can trigger out-of-bounds reads and writes in the Linux kernel RMI driver, leaking heap memory and potentially executing code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/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\nHID: rmi: fix OOB access with undersized RMI reports\n\nThe hid-rmi driver sizes its writeReport/readReport buffer purely from\nthe report descriptor supplied by the device, with no minimum bound:\n\n\tdata-\u003einput_report_size  = hid_report_len(input_report);\n\tdata-\u003eoutput_report_size = hid_report_len(output_report);\n\talloc_size = data-\u003eoutput_report_size + data-\u003einput_report_size;\n\tdata-\u003ewriteReport = devm_kzalloc(\u0026hdev-\u003edev, alloc_size, GFP_KERNEL);\n\tdata-\u003ereadReport = data-\u003ewriteReport + data-\u003eoutput_report_size;\n\nbut then reads and writes fixed offsets into it.  A device declaring a\n1-byte output and a 1-byte input report makes hid_report_len() return 2\nfor each, so alloc_size is 4, while rmi_set_page() -- reached\nunconditionally at probe time through rmi_input_configured() -- stores\nwriteReport[4] and rmi_hid_read_block() stores writeReport[0..5].  Since\nreadReport lives at writeReport + output_report_size, those stores also\ncorrupt the window the next reply is parsed out of.\n\nThe read path is worse: the copy length comes from readReport[1], which\nthe device fills in and can be up to 255, and the copy starts at\n\u0026readReport[2] with no regard for input_report_size, so it runs past the\nend of the allocation into adjacent slab objects.  This does not even\nneed a lying device -- rmi_f01_probe() issues a fixed 21-byte register\nread, so any device declaring an input report smaller than 23 bytes\nreads out of bounds even when it answers truthfully.  Those bytes become\nthe register values the RMI core acts on: rmi_f01_probe() prints them to\nthe kernel log as the product id and exports them through the mode 0444\nsysfs attribute of the same name, and rmi_driver_set_irq_bits() sends\nthem back to the device as the interrupt mask, so an undersized report\ndescriptor leaks heap contents both to unprivileged userspace and to the\ndevice itself.\n\nThe write path has no bound either: rmi_hid_write_block() copies an\nunbounded len to \u0026writeReport[4], and the largest caller a device can\ndrive at probe time is rmi_driver_set_irq_bits(), whose length is\nderived from the interrupt source counts the device declares in its Page\nDescription Table.\n\nFinally, the read loop cannot terminate on a zero-length reply: such a\nreply copies nothing and advances neither bytes_read nor bytes_needed,\nand because a reply did arrive the one second wait_event_timeout() does\nnot fire either, so a device answering 0 forever keeps the loop running\ninside the probe worker with page_mutex held.  khungtaskd does not\nnotice, because every reply wakes the task.\n\nReject reports too small for what the driver builds -- 6 output bytes\nfor the write reports and 3 input bytes for the read handshake -- at\nprobe time, clamp the write and the read copy to the report sizes the\ndevice declared, and treat a zero-length reply as an error.  A device\nrefused this way is started as an ordinary HID device, like one that\ndoes not carry the RMI report ids at all.\n\nRMI_DEVICE must not be left set in device_flags on that path, because\nrmi_input_configured() would then run the RMI setup and reach\nrmi_set_page(), which writes the writeReport buffer the refusal just\nskipped allocating.  The bit can arrive set: rmi_probe() copies\nid-\u003edriver_data into device_flags before the report checks, and a bind\nthrough the new_id sysfs attribute can supply driver_data with\nRMI_DEVICE (BIT(0)) set.  Strip the bit where driver_data is copied, so\nRMI_DEVICE keeps meaning exactly \"this probe validated the reports\"; the\nthree jumps to start that predate this patch are covered as well.\n\nThe error path also clears RMI_READ_DATA_PENDING on its way out, because\nthat flag is what the wait at the top of the loop tests: leaving it set\nwould make every later wait_event_timeout() return immediately on the\nstale reply and kill the read path for the rest of the device's life.\n\nClamping does not regress working hardware: the read loop already\nhandles\n---truncated---","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: rmi: fix OOB access with undersized RMI reports","id":"CVE-2026-90000","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":"HID: bpf: serialize device reference release in struct_ops destroy path","id":"CVE-2026-90001"},"packages":[],"prev":{"headline":"HID: wacom: validate report length in wacom_intuos_pro2_bt_irq","id":"CVE-2026-89999"},"products":["Linux"],"published":"2026-09-16","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 malicious or undersized HID device can trigger out-of-bounds reads and writes in the Linux kernel RMI driver, leaking heap memory and potentially executing code.","url":"https://insights.sbomify.com/CVE-2026-90000/"}