CVE-2005-3848

Description

Memory leak in the icmp_push_reply function in Linux 2.6 before 2.6.12.6 and 2.6.13 allows remote attackers to cause a denial of service (memory consumption) via a large number of crafted packets that cause the ip_append_data function to fail, aka "DST leak in icmp_push_reply."

7.8

CVSS

Severity: High

CVSS 2.0 •

EPSS 6.70% Top 10%

Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory debian.org Vendor Advisory suse.de Vendor Advisory mandriva.com Vendor Advisory debian.org Vendor Advisory ubuntu.com

Affected: n/a n/a

References

Link	Tags
http://www.redhat.com/support/errata/RHSA-2006-0140.html	vendor advisory
http://secunia.com/advisories/19038	third party advisory
http://marc.info/?l=linux-kernel&m=112431016816937&w=2	mailing list
http://marc.info/?l=linux-kernel&m=112508479212728&w=2	mailing list
http://secunia.com/advisories/19369	third party advisory
http://secunia.com/advisories/18203	third party advisory
http://www.redhat.com/support/errata/RHSA-2006-0101.html	vendor advisory
http://www.securityfocus.com/bid/16044	vdb entry
http://www.debian.org/security/2006/dsa-1018	vendor advisory
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=cb94c62c252796f42bb83fe40960d12f3ea5a82a
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11346	vdb entry signature
http://secunia.com/advisories/18510	third party advisory
http://lists.suse.de/archive/suse-security-announce/2006-Feb/0010.html	vendor advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2006:072	vendor advisory
http://www.debian.org/security/2006/dsa-1017	vendor advisory
http://www.kernel.org/git/?p=linux/kernel/git/chrisw/stable-queue.git%3Ba=blob%3Bh=1cf41a8a8db3080c9a9243e77c5c447c8e694f87%3Bhb=9c5fcb99af7c157be45e9d53aeb857ded5211fcd%3Bf=2.6.12.6/fix-dst-leak-in-icmp_push_reply.patch
http://secunia.com/advisories/19374	third party advisory
http://marc.info/?l=linux-kernel&m=112439084918917&w=2	mailing list
https://usn.ubuntu.com/231-1/	vendor advisory
http://secunia.com/advisories/18562	third party advisory

Frequently Asked Questions

What is the severity of CVE-2005-3848?: CVE-2005-3848 has been scored as a high severity vulnerability.
How to fix CVE-2005-3848?: To fix CVE-2005-3848, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2005-3848 being actively exploited in the wild?: It is possible that CVE-2005-3848 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~7% probability that this vulnerability will be exploited by malicious actors in the next 30 days.