{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93828 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93828 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-93828 and fix it if it is affected.\n\nWhat it is: CVE-2026-93828 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-93828 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-93828/ (Markdown: https://insights.sbomify.com/CVE-2026-93828/index.md)","id":"CVE-2026-93828","markdown":"https://insights.sbomify.com/CVE-2026-93828/index.md","name":"CVE-2026-93828","record":{"aliases":["AZL-103604","BELL-CVE-2026-93828","DEBIAN-CVE-2026-93828","GHSA-crx7-9vj2-jqgc","UBUNTU-CVE-2026-93828"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel exFAT","requires_auth":"none","summary":"An integer overflow in the Linux kernel exFAT driver causes an infinite loop when processing a damaged volume with a zero-sized upcase table.","user_interaction":"required","vuln_class":"integer_overflow"},"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\nexfat: fix handling of damaged volume in exfat_create_upcase_table()\n\nWhen the size of the upcase table is set to zero in the dentry for any\nreason(e.g. corrupted media or misbehaving device), an integer overflow\ncauses the module to loop indefinitely.\n\nIf the size of the upcase table is read zero, do not attempt to load the\ntable. Instead, fallback to loading the default upcase table. If the\nsize of the upcase table is zero or no upcase table is found, raise\nexfat_fs_error() to mark the volume read-only.","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":"exfat: fix handling of damaged volume in exfat_create_upcase_table()","id":"CVE-2026-93828","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"smb: client: fix races in cifsd thread creation","id":"CVE-2026-93829"},"packages":[],"prev":{"headline":"virtio-fs: avoid double-free on failed queue setup","id":"CVE-2026-93827"},"products":["Linux"],"published":"2026-09-24","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-21","vendors":["Linux"]},"summary":"An integer overflow in the Linux kernel exFAT driver causes an infinite loop when processing a damaged volume with a zero-sized upcase table.","url":"https://insights.sbomify.com/CVE-2026-93828/"}