{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2021-1001525 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2021-1001525 yet. Limit exposure of the affected software until one is available.","what":"GSD-2021-1001525 is a memory corruption vulnerability in Kernel, published on 19 Oct 2021."},"fix_prompt":"Check this codebase for GSD-2021-1001525 and fix it if it is affected.\n\nWhat it is: GSD-2021-1001525 is a memory corruption vulnerability in Kernel, published on 19 Oct 2021. \nExploitation: There is no known exploitation of GSD-2021-1001525 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Kernel (Linux): affected all versions; no fix listed\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/GSD-2021-1001525/ (Markdown: https://insights.sbomify.com/GSD-2021-1001525/index.md)","id":"GSD-2021-1001525","markdown":"https://insights.sbomify.com/GSD-2021-1001525/index.md","name":"GSD-2021-1001525","record":{"aliases":[],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux Kernel","requires_auth":"none","summary":"A memory leak in the Linux Kernel MDIO PHY driver could allow an attacker to cause a denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"phy: mdio: fix memory leak\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.251 by commit f4f502a04ee1e543825af78f47eb7785015cd9f6, it was introduced in version v2.6.28 by commit 46abc02175b3c246dd5141d878f565a8725060c9. For more details please see the references link.","ecosystems":["Linux"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"phy: mdio: fix memory leak","id":"GSD-2021-1001525","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Linux","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Linux","fixed":[],"introduced":[],"last_affected":[],"package":"Kernel","purl":null,"source":"GSD-2021-1001525"}],"products":null,"published":"2021-10-19","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"Global Security Database","prefix":"GSD"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A memory leak in the Linux Kernel MDIO PHY driver could allow an attacker to cause a denial of service.","url":"https://insights.sbomify.com/GSD-2021-1001525/"}