{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63908 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-63908 is a memory corruption vulnerability in Linux, published on 19 Jul 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-63908 and fix it if it is affected.\n\nWhat it is: CVE-2026-63908 is a memory corruption vulnerability in Linux, published on 19 Jul 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-63908 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-63908/ (Markdown: https://insights.sbomify.com/CVE-2026-63908/index.md)","id":"CVE-2026-63908","markdown":"https://insights.sbomify.com/CVE-2026-63908/index.md","name":"CVE-2026-63908","record":{"aliases":["BELL-CVE-2026-63908","DEBIAN-CVE-2026-63908","GHSA-g59q-3pwp-9gcx","ROOT-OS-UBUNTU-2204-CVE-2026-63908","UBUNTU-CVE-2026-63908"],"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 driver","requires_auth":"none","summary":"A boundary check error in the Atmel MXT touch driver allows memory corruption, potentially enabling local attackers to execute code or escalate privileges.","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\nInput: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem\n\nWhen a configuration file provides an object size that is larger than the\ndriver's known mxt_obj_size(object), the driver intends to discard the\nextra bytes.\n\nThe loop iterates using for (i = 0; i \u003c size; i++). Inside the loop, the\ncondition to skip processing extra bytes is:\n\n    if (i \u003e mxt_obj_size(object))\n        continue;\n\nSince i is a 0-based index, the valid indices for the object are 0 through\nmxt_obj_size(object) - 1.\n\nWhen i == mxt_obj_size(object), the condition evaluates to false, and the\ncode processes the byte instead of discarding it.\n\nThis causes the code to calculate byte_offset = reg + i - cfg-\u003estart_ofs\nand writes the byte there, overwriting exactly one byte of the adjacent\ninstance or object.\n\nUpdate the boundary check to skip extra bytes correctly by using \u003e=.","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":"Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem","id":"CVE-2026-63908","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":"ksmbd: OOB read regression in smb_check_perm_dacl() ACE-walk loops","id":"CVE-2026-63909"},"packages":[],"prev":{"headline":"uio: uio_pci_generic_sva: fix double free of devm_kzalloc() memory","id":"CVE-2026-63907"},"products":["Linux"],"published":"2026-07-19","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-07-19","vendors":["Linux"]},"summary":"A boundary check error in the Atmel MXT touch driver allows memory corruption, potentially enabling local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-63908/"}