LiveActive security incident?Get immediate response
CVE Record

CVE-2013-4470: The Linux kernel before 3.12, when UDP Fragmentation Offload (UFO) is enabled, does not properly initialize...

The Linux kernel before 3.12, when UDP Fragmentation Offload (UFO) is enabled, does not properly initialize certain data structures, which allows local users to cause a denial of service (memory corruption and system crash) or possibly gain privileges via a crafted application that uses the UDP_CORK option in a setsockopt system call and sends both short and long packets, related to the ip_ufo_append_data function in net/ipv4/ip_output.c and the ip6_ufo_append_data function in net/ipv6/ip6_output.c.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-4470 is an old Linux kernel flaw in UDP Fragmentation Offload handling. A local user or local workload could trigger kernel memory corruption, causing a system crash and possibly privilege escalation. It matters most for legacy Linux systems or appliances still running kernels before 3.12 or vendor kernels that lack the listed fixes. Exposure is mainly legacy Linux systems, embedded products, appliances, or long-lived distro kernels that did not receive the relevant backported vendor fixes. The attacker position is local user or local code execution, not unauthenticated remote network access based on the provided sources. Treat this as a legacy-kernel hygiene issue with elevated priority on shared or multi-tenant Linux systems. It is not shown as actively exploited in the provided sources, but kernel crashes and possible local privilege escalation can create serious business impact where old systems remain in production. Mitigation focus: Upgrade to a vendor-supported kernel containing the upstream fixes.; Prioritize systems running Linux kernels before 3.12 or unfixed vendor backports.; Review Ubuntu, Red Hat, and SUSE advisories for affected package versions..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-4470 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.