{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89953 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89953 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-89953 and fix it if it is affected.\n\nWhat it is: CVE-2026-89953 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-89953 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-89953/ (Markdown: https://insights.sbomify.com/CVE-2026-89953/index.md)","id":"CVE-2026-89953","markdown":"https://insights.sbomify.com/CVE-2026-89953/index.md","name":"CVE-2026-89953","record":{"aliases":["AZL-101562","BELL-CVE-2026-89953","DEBIAN-CVE-2026-89953","GHSA-wvj7-v5wh-67w6","UBUNTU-CVE-2026-89953"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A memory leak in the Linux kernel mtdoops driver allows local attackers to exhaust memory by repeatedly removing and re-adding MTD devices.","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\nmtd: mtdoops: free page bitmap when the backing MTD is removed\n\nmtdoops_notify_add() allocates oops_page_used when the configured MTD\ndevice is registered.  mtdoops_notify_remove() detaches from that device\nbut leaves the bitmap allocated.  If the same MTD device is later\nregistered again, the add path allocates a new bitmap and overwrites the\nold pointer, leaking one vmalloc allocation per remove/add cycle.\n\nThis is only visible when the backing MTD device can disappear and be\nregistered again while mtdoops remains loaded, so the usual static MTD\ncase does not expose it.\n\nFree the bitmap after unregistering the dumper and flushing the pending\nworkers, then clear the pointer and page count before a later attach can\nallocate fresh state.  Clearing the pointer also keeps the module exit\npath from freeing the same bitmap a second time after a remove event.","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: mtdoops: free page bitmap when the backing MTD is removed","id":"CVE-2026-89953","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":"mtd: afs: validate v2 image info bounds","id":"CVE-2026-89954"},"packages":[],"prev":{"headline":"mtd: rawnand: validate ONFI extended parameter page sections","id":"CVE-2026-89952"},"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 memory leak in the Linux kernel mtdoops driver allows local attackers to exhaust memory by repeatedly removing and re-adding MTD devices.","url":"https://insights.sbomify.com/CVE-2026-89953/"}