{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98488 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98488 is a denial of service 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-98488 and fix it if it is affected.\n\nWhat it is: CVE-2026-98488 is a denial of service 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-98488 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-98488/ (Markdown: https://insights.sbomify.com/CVE-2026-98488/index.md)","id":"CVE-2026-98488","markdown":"https://insights.sbomify.com/CVE-2026-98488/index.md","name":"CVE-2026-98488","record":{"aliases":["AZL-108692","BELL-CVE-2026-98488","DEBIAN-CVE-2026-98488","GHSA-5jr3-mhw7-v4fq","UBUNTU-CVE-2026-98488"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A flaw in the atl1e network driver causes a soft lockup when hardware reports an out-of-range value, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: atl1e: fix soft lockup on out-of-range hw_next_to_clean read\n\nSame issue as atl1c (see the first commit in this series, \"net:\natl1c: fix soft lockup on out-of-range tpd_cons read\"): the hardware\ncan report an out-of-range hw_next_to_clean (seen as 0xffff) while\nthe PCIe link/MAC is resetting. An out-of-range value can never be\nreached and the loop below would spin forever. Treat it as \"nothing\nnew to clean\" instead.","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: atl1e: fix soft lockup on out-of-range hw_next_to_clean read","id":"CVE-2026-98488","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net: atl1c: fix soft lockup on out-of-range tpd_cons read","id":"CVE-2026-98489"},"packages":[],"prev":{"headline":"net: bridge: mdb: restart port group walk after deletion","id":"CVE-2026-98487"},"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 flaw in the atl1e network driver causes a soft lockup when hardware reports an out-of-range value, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-98488/"}