{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90300 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90300 is a vulnerability in Linux, published on 17 Sep 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-90300 and fix it if it is affected.\n\nWhat it is: CVE-2026-90300 is a vulnerability in Linux, published on 17 Sep 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-90300 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-90300/ (Markdown: https://insights.sbomify.com/CVE-2026-90300/index.md)","id":"CVE-2026-90300","markdown":"https://insights.sbomify.com/CVE-2026-90300/index.md","name":"CVE-2026-90300","record":{"aliases":["AZL-102008","BELL-CVE-2026-90300","DEBIAN-CVE-2026-90300","GHSA-ghq7-v2f8-82jr","UBUNTU-CVE-2026-90300"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker with BPF privileges can read uninitialized kernel memory via stack trace helpers, potentially leaking sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nbpf: Clear buf on error in __bpf_get_task_stack\n\nBoth bpf_get_task_stack and bpf_get_task_stack_sleepable helpers that\nuse __bpf_get_task_stack have buf defined as ARG_PTR_TO_UNINIT_MEM\nargument and we should initialize the buf on every return path.\n\nAdding missing buf memset for __bpf_get_task_stack fail paths. This\nprovides deterministic buffer contents, which is useful when the buffer\nis used directly as a map key.","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":"bpf: Clear buf on error in __bpf_get_task_stack","id":"CVE-2026-90300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ocfs2: o2hb: quiesce negotiate handlers and timeout work","id":"CVE-2026-90301"},"packages":[],"prev":{"headline":"bpf: Fix sleepable check for tracing/lsm prog","id":"CVE-2026-90299"},"products":["Linux"],"published":"2026-09-17","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 local attacker with BPF privileges can read uninitialized kernel memory via stack trace helpers, potentially leaking sensitive data.","url":"https://insights.sbomify.com/CVE-2026-90300/"}