{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2009-3624 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-3624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-3624 is a medium-severity use after free vulnerability in Linux kernel, published on 2 Nov 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-3624 and fix it if it is affected.\n\nWhat it is: CVE-2009-3624 is a medium-severity use after free vulnerability in Linux kernel, published on 2 Nov 2009. 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-2009-3624 in the wild and no public exploit code.\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-3624/ (Markdown: https://insights.sbomify.com/CVE-2009-3624/index.md)","id":"CVE-2009-3624","markdown":"https://insights.sbomify.com/CVE-2009-3624/index.md","name":"CVE-2009-3624","record":{"aliases":["GHSA-gx7p-6h8g-757g"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Local attackers can exploit a reference counting error in the Linux kernel keyring subsystem to escalate privileges or cause a system crash.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"kernel","vendor":"linux"},{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"The get_instantiation_keyring function in security/keys/keyctl.c in the KEYS subsystem in the Linux kernel before 2.6.32-rc5 does not properly maintain the reference count of a keyring, which allows local users to gain privileges or cause a denial of service (OOPS) via vectors involving calls to this function without specifying a keyring by ID, as demonstrated by a series of keyctl request2 and keyctl list commands.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Use after free in n/a","id":"CVE-2009-3624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"use_after_free","year":"2009"},"n_packages":0,"n_references":9,"next":{"headline":"Path traversal in n/a","id":"CVE-2009-3625"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2009-3623"},"products":["n/a"],"published":"2009-11-02","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.9,"headline":"Information disclosure in n/a","id":"CVE-2009-2847","kev_date_added":null,"published":"2009-08-18"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local attackers can exploit a reference counting error in the Linux kernel keyring subsystem to escalate privileges or cause a system crash.","url":"https://insights.sbomify.com/CVE-2009-3624/"}