{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-7229 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-7229 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-7229 is a high-severity denial of service vulnerability in n/a, published on 15 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-7229 and fix it if it is affected.\n\nWhat it is: CVE-2006-7229 is a high-severity denial of service vulnerability in n/a, published on 15 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-7229 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2006-7229/ (Markdown: https://insights.sbomify.com/CVE-2006-7229/index.md)","id":"CVE-2006-7229","markdown":"https://insights.sbomify.com/CVE-2006-7229/index.md","name":"CVE-2006-7229","record":{"aliases":["GHSA-c96x-hvmf-4pcg"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"Remote attackers can crash the system via network traffic floods due to improper locking in the skge driver.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"linux_kernel","vendor":"ubuntu"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-399","name":null},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"The skge driver 1.5 in Linux kernel 2.6.15 on Ubuntu does not properly use the spin_lock and spin_unlock functions, which allows remote attackers to cause a denial of service (machine crash) via a flood of network traffic.","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":"Denial of service in n/a","id":"CVE-2006-7229","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2006"},"n_packages":0,"n_references":4,"next":{"headline":"Denial of service in n/a","id":"CVE-2006-7230"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2006-7228"},"products":["n/a"],"published":"2007-11-15","related":[],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-03","vendors":["n/a"]},"summary":"Remote attackers can crash the system via network traffic floods due to improper locking in the skge driver.","url":"https://insights.sbomify.com/CVE-2006-7229/"}