{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72058 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72058 is a memory corruption vulnerability in Linux, published on 15 Aug 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-72058 and fix it if it is affected.\n\nWhat it is: CVE-2026-72058 is a memory corruption vulnerability in Linux, published on 15 Aug 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-72058 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-72058/ (Markdown: https://insights.sbomify.com/CVE-2026-72058/index.md)","id":"CVE-2026-72058","markdown":"https://insights.sbomify.com/CVE-2026-72058/index.md","name":"CVE-2026-72058","record":{"aliases":["BELL-CVE-2026-72058","DEBIAN-CVE-2026-72058","GHSA-c9wj-7pm2-vx6f","UBUNTU-CVE-2026-72058"],"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 memory management error in the ixp4xx_hss driver causes use-after-free or double-free conditions, potentially leading to system crashes or arbitrary code execution.","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: ixp4xx_hss: fix duplicate HDLC netdev allocation\n\nixp4xx_hss_probe() allocates two HDLC netdevs. The first one is stored\nin ndev, initialized, and registered with register_hdlc_device(). The\nsecond one is stored in port-\u003enetdev and later used by the remove path\nfor unregister_hdlc_device() and free_netdev().\n\nThis means that the registered netdev is not the same object that is\nunregistered and freed on remove. It also leaks the first allocation if\nthe second alloc_hdlcdev() call fails, and the first allocation is not\nchecked before ndev is used.\n\nOlder code allocated the HDLC netdev only once and stored the same object\nin both the local variable and port-\u003enetdev. The buggy conversion split\nthis into two alloc_hdlcdev() calls. A later rename changed the local\nvariable name to ndev, but the underlying mismatch remained.\n\nFix this by allocating the HDLC netdev only once and assigning the same\nobject to port-\u003enetdev.","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: ixp4xx_hss: fix duplicate HDLC netdev allocation","id":"CVE-2026-72058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"net: wwan: t7xx: destroy DMA pool on CLDMA late init failure","id":"CVE-2026-72059"},"packages":[],"prev":{"headline":"net/sched: act_ct: preserve tc_skb_cb across defragmentation","id":"CVE-2026-72057"},"products":["Linux"],"published":"2026-08-15","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-08-23","vendors":["Linux"]},"summary":"A memory management error in the ixp4xx_hss driver causes use-after-free or double-free conditions, potentially leading to system crashes or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2026-72058/"}