{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89596 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89596 is a high-severity memory corruption vulnerability in Linux, published on 11 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-89596 and fix it if it is affected.\n\nWhat it is: CVE-2026-89596 is a high-severity memory corruption vulnerability in Linux, published on 11 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-89596 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-89596/ (Markdown: https://insights.sbomify.com/CVE-2026-89596/index.md)","id":"CVE-2026-89596","markdown":"https://insights.sbomify.com/CVE-2026-89596/index.md","name":"CVE-2026-89596","record":{"aliases":["AZL-100386","BELL-CVE-2026-89596","DEBIAN-CVE-2026-89596","GHSA-2x8h-gf2x-f48m","UBUNTU-CVE-2026-89596"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"An off-by-one error in the forcedeth network driver causes out-of-bounds memory access during suspend/resume, potentially crashing the kernel if UBSAN trapping is enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nforcedeth: fix off-by-one when saving/restoring non-PCI config space\n\nnv_suspend() and nv_resume() walk the non-PCI configuration space with\n\n\tfor (i = 0; i \u003c= np-\u003eregister_size/sizeof(u32); i++)\n\nwhich runs one iteration too many. saved_config_space is declared as\n\n\tu32 saved_config_space[NV_PCI_REGSZ_MAX/4];\n\nand NV_PCI_REGSZ_VER3 is equal to NV_PCI_REGSZ_MAX (0x604), so on a VER3\ndevice register_size/sizeof(u32) is exactly the array length and the last\niteration addresses one element past the end.\n\nThe element it lands on is np-\u003ename_rx[0..3]: saved_config_space[] is\nfollowed immediately by char name_rx[IFNAMSIZ + 3], and char needs no\npadding. Nothing observable is corrupted by that, because nv_request_irq()\nrewrites name_rx with sprintf() before it is ever passed to request_irq().\nThe bug is the out-of-bounds access itself, which UBSAN reports and which\nCONFIG_UBSAN_TRAP=y turns into a trap that aborts the running kernel code,\nplus an MMIO read and, on resume, an MMIO writel() to base + 0x604, one\ndword past the range the driver mapped:\n\n\tnp-\u003ebase = ioremap(addr, np-\u003eregister_size);\n\nVER1 and VER2 devices stay inside the array, but they too get the stray\nread and the stray write one dword past their own window.\n\nCaught by UBSAN on an Apple Macmini3,1 (MCP79) during a deep S3 cycle.\nThe splat below is trimmed: the build path in the file name, the CPU\nand taint lines, the Workqueue line, the \"?\" hint frames, and the\nframes below device_suspend are all cut. The kernel was tainted, with\nan out-of-tree nouveau and CPU_OUT_OF_SPEC; forcedeth itself was the\nstock module.\n\n  UBSAN: array-index-out-of-bounds in drivers/net/ethernet/nvidia/forcedeth.c:6225:25\n  index 385 is out of range for type 'u32 [385]'\n  Call Trace:\n   dump_stack_lvl+0x5d/0x80\n   ubsan_epilogue+0x5/0x2b\n   __ubsan_handle_out_of_bounds.cold+0x54/0x59\n   __this_module+0xe398c/0xe9010 [forcedeth]\n   pci_pm_suspend+0x80/0x170\n   dpm_run_callback+0x51/0x160\n   device_suspend+0x1a2/0x4a0\n   ...\n\nBoth loops are hit. UBSAN reports each source location only once per module\nload (__ubsan_handle_out_of_bounds() calls suppress_report(), which does\ntest_and_set_bit(REPORTED_BIT, ...) on the struct source_location), so the\ntwo splats land in the first S3 cycle after the module is loaded and later\ncycles are silent even though the access still runs off the end every time.\nIn that first cycle line 6225 is reported from pci_pm_suspend and line 6240\nfrom pci_pm_resume.\n\nThe same off-by-one was fixed in nv_get_regs() by commit ba9aa134287f\n(\"forcedeth: fix buffer overflow\") in 2012; these two loops were missed.\nThe suspend and resume side was reported on LKML in September 2013 by Marc\nWeber, with the same analysis and the same one-character fix, but the patch\nwas attached rather than sent inline and the thread ended there.\n\nUse \u003c instead of \u003c=, which saves and restores exactly register_size bytes.","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":"forcedeth: fix off-by-one when saving/restoring non-PCI config space","id":"CVE-2026-89596","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":"fbdev: uvesafb: unregister connector callback on init failure","id":"CVE-2026-89597"},"packages":[],"prev":{"headline":"fsnotify: Fix stale object mask after concurrent mark updates","id":"CVE-2026-89595"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An off-by-one error in the forcedeth network driver causes out-of-bounds memory access during suspend/resume, potentially crashing the kernel if UBSAN trapping is enabled.","url":"https://insights.sbomify.com/CVE-2026-89596/"}