{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98592 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98592 is an use after free vulnerability in Linux, published on 18 Oct 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-98592 and fix it if it is affected.\n\nWhat it is: CVE-2026-98592 is an use after free vulnerability in Linux, published on 18 Oct 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-98592 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-98592/ (Markdown: https://insights.sbomify.com/CVE-2026-98592/index.md)","id":"CVE-2026-98592","markdown":"https://insights.sbomify.com/CVE-2026-98592/index.md","name":"CVE-2026-98592","record":{"aliases":["BELL-CVE-2026-98592","DEBIAN-CVE-2026-98592","GHSA-f5v2-jrgp-7g6f","UBUNTU-CVE-2026-98592"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A use-after-free vulnerability in the SpacemiT EMAC driver allows attackers to cause denial of service or potentially execute code via crafted network traffic.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nnet: spacemit: clear TX descriptor on fragment mapping failure\n\nemac_tx_mem_map() writes TX_DESC_0_OWN into the ring descriptor for\nevery slot beyond old_head as soon as that slot's memset()'d local\ncopy is committed with \"*tx_desc_addr = tx_desc\", i.e. before the\nbuffers for that slot have necessarily all been mapped successfully.\nIf emac_tx_map_frag() then fails on a later fragment, the err_free_skb\npath calls emac_free_tx_buf() to unmap and drop the skb, but leaves\nthe already-written descriptor memory untouched, and tx_ring-\u003ehead is\nnever advanced past old_head (the \"tx_ring-\u003ehead = head\" store is\nskipped by the goto).\n\nSo a slot between old_head and the rolled-back head can be left with\nTX_DESC_0_OWN set and buffer_addr_{1,2} pointing at DMA mappings that\nemac_free_tx_buf() just tore down, while software considers that slot\nfree again. The next successful emac_tx_mem_map() call only rebuilds\nold_head itself; if the DMA engine auto-advances into the following\ndescriptor once it finishes old_head's packet, it will fetch that\nstale, already-unmapped address.\n\nemac_tx_clean_desc() already treats emac_free_tx_buf() and clearing\nthe descriptor as a pair when reclaiming completed descriptors; do\nthe same in the mapping failure path.","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":"net: spacemit: clear TX descriptor on fragment mapping failure","id":"CVE-2026-98592","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"s390/debug: Fix NULL pointer dereference in debug_info_copy()","id":"CVE-2026-98593"},"packages":[],"prev":{"headline":"bpf: Fix bounds check for skb-backed dynptrs","id":"CVE-2026-98591"},"products":["Linux"],"published":"2026-10-18","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 use-after-free vulnerability in the SpacemiT EMAC driver allows attackers to cause denial of service or potentially execute code via crafted network traffic.","url":"https://insights.sbomify.com/CVE-2026-98592/"}