{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89879 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89879 is a 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-89879 and fix it if it is affected.\n\nWhat it is: CVE-2026-89879 is a 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-89879 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-89879/ (Markdown: https://insights.sbomify.com/CVE-2026-89879/index.md)","id":"CVE-2026-89879","markdown":"https://insights.sbomify.com/CVE-2026-89879/index.md","name":"CVE-2026-89879","record":{"aliases":["AZL-101298","BELL-CVE-2026-89879","DEBIAN-CVE-2026-89879","GHSA-w8vh-2wxg-frpg","UBUNTU-CVE-2026-89879"],"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":"none","summary":"A malicious USB device can trigger a buffer overflow in the s2255 kernel driver, potentially leading to code execution or system crash.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nmedia: s2255: bound JPEG frame size before copying into the buffer\n\ns2255_fillbuff() memcpy()s vc-\u003ejpg_size bytes of a captured JPEG/MJPEG\nframe into the vb2 plane.  vc-\u003ejpg_size is taken verbatim from the\nS2255_MARKER_FRAME header the device sends (pdword[4] in save_frame())\nand, unlike the frame payload length just above it, is never bounded:\n\n\tpayload = le32_to_cpu(pdword[3]);\n\tif (payload \u003e vc-\u003ereq_image_size)\t/* payload is checked ... */\n\t\treturn -EINVAL;\n\tvc-\u003epkt_size = payload;\n\tvc-\u003ejpg_size = le32_to_cpu(pdword[4]);\t/* ... jpg_size is not */\n\nA malicious or malfunctioning device can therefore report a jpg_size\nlarger than the destination vb2 plane, and the memcpy() writes past it.\njpg_size is a signed int, so a value with the top bit set also turns\ninto a huge length.\n\nReject a frame whose jpg_size is negative or exceeds the plane size\nbefore copying it.","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":"media: s2255: bound JPEG frame size before copying into the buffer","id":"CVE-2026-89879","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":"media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure","id":"CVE-2026-89880"},"packages":[],"prev":{"headline":"media: s2255: check firmware size before reading trailing marker","id":"CVE-2026-89878"},"products":["Linux"],"published":"2026-09-16","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 malicious USB device can trigger a buffer overflow in the s2255 kernel driver, potentially leading to code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-89879/"}