{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93048 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93048 is a vulnerability in Linux, published on 17 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-93048 and fix it if it is affected.\n\nWhat it is: CVE-2026-93048 is a vulnerability in Linux, published on 17 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-93048 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-93048/ (Markdown: https://insights.sbomify.com/CVE-2026-93048/index.md)","id":"CVE-2026-93048","markdown":"https://insights.sbomify.com/CVE-2026-93048/index.md","name":"CVE-2026-93048","record":{"aliases":["AZL-102063","BELL-CVE-2026-93048","DEBIAN-CVE-2026-93048","GHSA-2p6r-8jww-x7j3","UBUNTU-CVE-2026-93048"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger an integer underflow in the Linux kernel MTD subsystem via BLKPG ioctl, causing a warning and potential denial of service.","user_interaction":"not_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\nmtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition()\n\nmtd_add_partition() does not reject the special offset value\nMTDPART_OFS_RETAIN (-3), which leads to a WARN_ON in\nadd_mtd_device() when called through the BLKPG ioctl on NAND\ndevices. The RETAIN value depends on cur_offset being the end of\nthe previous partition, but in the dynamic partition path\ncur_offset equals the offset argument itself, causing undefined\nbehavior.\n\nCommit 5daa7b21496a (\"mtd: prepare partition add and del functions\nfor ioctl requests\") introduced mtd_add_partition() and correctly\nrejected MTDPART_OFS_APPEND (-1) and MTDPART_OFS_NXTBLK (-2),\nsince those special offsets rely on cur_offset tracking the\nprevious partition's end. However, commit 1a31368bf92e (\"mtd: add a flags\nfor partitions which should just leave smth. after them\")\nlater added MTDPART_OFS_RETAIN (-3) for the static\npartition table path without updating mtd_add_partition() to\nalso reject this value.\n\nWith offset=-3 passed via BLKPG, the RETAIN size calculation in\nallocate_partition() underflows (parent_size - 0xFFFFFFFFFFFFFFFD\n= parent_size + 3). If the underflow result does not appear to\nleave enough space, allocate_partition() jumps to out_register via\ngoto, skipping erasesize initialization. This results in\nerasesize=0, which triggers:\n\nWARN_ON((!mtd-\u003eerasesize || !master-\u003e_erase) \u0026\u0026\n\t\t!(mtd-\u003eflags \u0026 MTD_NO_ERASE))\n\nin add_mtd_device(). If the underflow result appears to leave\nenough space, a bogus partition size is calculated, but the\n\"out of reach\" sanity check catches the invalid offset and\ncreates a disabled empty partition (offset=0, size=0) instead\nof returning an error.\n\nFix this by adding MTDPART_OFS_RETAIN to the rejection list in\nmtd_add_partition(), consistent with the existing handling of\nAPPEND and NXTBLK.","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":"mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition()","id":"CVE-2026-93048","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"mtd: mtdswap: Avoid freeing registered blktrans device twice","id":"CVE-2026-93049"},"packages":[],"prev":{"headline":"drm/v3d: Associate BOs with every job that accesses them","id":"CVE-2026-93047"},"products":["Linux"],"published":"2026-09-17","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 can trigger an integer underflow in the Linux kernel MTD subsystem via BLKPG ioctl, causing a warning and potential denial of service.","url":"https://insights.sbomify.com/CVE-2026-93048/"}