{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98493 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98493 is a memory corruption 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-98493 and fix it if it is affected.\n\nWhat it is: CVE-2026-98493 is a memory corruption 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-98493 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-98493/ (Markdown: https://insights.sbomify.com/CVE-2026-98493/index.md)","id":"CVE-2026-98493","markdown":"https://insights.sbomify.com/CVE-2026-98493/index.md","name":"CVE-2026-98493","record":{"aliases":["AZL-108671","BELL-CVE-2026-98493","DEBIAN-CVE-2026-98493","GHSA-x4fq-3fw2-872x","UBUNTU-CVE-2026-98493"],"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":"none","summary":"A buffer overflow in the Linux kernel DHCP option construction allows a local attacker to cause a system panic via crafted hostname and vendor-class options.","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\nnet: ipconfig: bound DHCP option construction\n\nic_dhcp_init_options() appends the hostname (option 12), vendor-class\n(option 60) and client-ID (option 61) options into the fixed 312-byte\nbootp_pkt.exten[] buffer.  Only the client-ID branch checked the\nremaining space; the hostname and vendor-class writes were unbounded.\n\nA 64-byte hostname together with the maximum 252-byte dhcpclass=\nidentifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available\nbytes even before the terminating END marker, so the vendor-class memcpy\nruns past the end of exten[].  With CONFIG_FORTIFY_SOURCE this is\nreported as a field-spanning write and, when the kernel is booted with\npanic_on_warn=1, aborts boot with a panic.\n\nRoute the optional options through a common helper that makes sure the\noption, its 2-byte header and the END marker all fit and drops an option\nthat would not.  Configurations with short options keep sending exactly\nthe same bytes as before.","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: ipconfig: bound DHCP option construction","id":"CVE-2026-98493","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"net: atl1: fix soft lockup on out-of-range cmb_tpd_next_to_clean read","id":"CVE-2026-98494"},"packages":[],"prev":{"headline":"net: macb: fix dma_alloc_coherent() leak on macb_alloc() error paths","id":"CVE-2026-98492"},"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-21","vendors":["Linux"]},"summary":"A buffer overflow in the Linux kernel DHCP option construction allows a local attacker to cause a system panic via crafted hostname and vendor-class options.","url":"https://insights.sbomify.com/CVE-2026-98493/"}