{"answers":{"affected":"1 open source package ship an affected version, including Kernel.","exploited":"There is no known exploitation of GSD-2021-1000528 in the wild and no public exploit code.","fix":"No fix has been published for GSD-2021-1000528 yet. Limit exposure of the affected software until one is available.","what":"GSD-2021-1000528 is a vulnerability in Kernel, published on 4 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GSD-2021-1000528 and fix it if it is affected.\n\nWhat it is: GSD-2021-1000528 is a vulnerability in Kernel, published on 4 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GSD-2021-1000528 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-1000528/ (Markdown: https://insights.sbomify.com/GSD-2021-1000528/index.md)","id":"GSD-2021-1000528","markdown":"https://insights.sbomify.com/GSD-2021-1000528/index.md","name":"GSD-2021-1000528","record":{"aliases":[],"analysis":{"component_type":"kernel","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"Uninitialized memory in the Linux kernel traffic control subsystem may allow attackers to read sensitive kernel data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"net: zero-initialize tc skb extension on allocation\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 v5.12.9 by commit 86ab133b695ed7ba1f8786b12f4ca43137ad8c18, it was introduced in version v5.9 by commit 038ebb1a713d114d54dbf14868a73181c0c92758. 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":"net: zero-initialize tc skb extension on allocation","id":"GSD-2021-1000528","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Linux","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"Linux","fixed":[],"introduced":[],"last_affected":[],"package":"Kernel","purl":null,"source":"GSD-2021-1000528"}],"products":null,"published":"2021-06-04","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":"Uninitialized memory in the Linux kernel traffic control subsystem may allow attackers to read sensitive kernel data.","url":"https://insights.sbomify.com/GSD-2021-1000528/"}