{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2847 exists.","fix":"Apply the vendor's patch.","what":"CVE-2009-2847 is a medium-severity vulnerability in Linux kernel, published on 18 Aug 2009. 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-2009-2847 and fix it if it is affected.\n\nWhat it is: CVE-2009-2847 is a medium-severity vulnerability in Linux kernel, published on 18 Aug 2009. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2847 exists.\n\nAffected product: Linux kernel. 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-2009-2847/ (Markdown: https://insights.sbomify.com/CVE-2009-2847/index.md)","id":"CVE-2009-2847","markdown":"https://insights.sbomify.com/CVE-2009-2847/index.md","name":"CVE-2009-2847","record":{"aliases":["GHSA-c85v-8h9f-3jwr"],"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":"Local attackers can read sensitive kernel stack data via sigaltstack on 64-bit Linux systems due to uncleared padding bytes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kernel","vendor":"linux"},{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:N/A:N","version":"2.0"},"cwes":[],"description":"The do_sigaltstack function in kernel/signal.c in Linux kernel 2.4 through 2.4.37 and 2.6 before 2.6.31-rc5, when running on 64-bit systems, does not clear certain padding bytes from a structure, which allows local users to obtain sensitive information from the kernel stack via the sigaltstack function.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-08-04","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-08-04","kind":"exploitdb","ref":"9352","stars":null,"title":"Linux Kernel 2.6.31-rc5 - sigaltstack 4-Byte Stack Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2009-2847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"information_disclosure","year":"2009"},"n_packages":0,"n_references":21,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2009-2848"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2009-2846"},"products":["n/a"],"published":"2009-08-18","related":[{"cvss_score":7.8,"headline":"Null dereference in n/a","id":"CVE-2009-2844","kev_date_added":null,"published":"2009-08-18"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2009-1389","kev_date_added":null,"published":"2009-06-16"},{"cvss_score":7.2,"headline":"Null dereference in n/a","id":"CVE-2009-2767","kev_date_added":null,"published":"2009-08-14"},{"cvss_score":6.9,"headline":"Memory corruption in n/a","id":"CVE-2009-2406","kev_date_added":null,"published":"2009-07-31"},{"cvss_score":6.8,"headline":"Denial of service in n/a","id":"CVE-2010-0309","kev_date_added":null,"published":"2010-02-12"},{"cvss_score":4.6,"headline":"Use after free in n/a","id":"CVE-2009-3624","kev_date_added":null,"published":"2009-11-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local attackers can read sensitive kernel stack data via sigaltstack on 64-bit Linux systems due to uncleared padding bytes.","url":"https://insights.sbomify.com/CVE-2009-2847/"}