Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2017-7308: Linux AF_PACKET packet_set_ring Out-of-Bounds Write

Published Mar 29, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS17.8%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Linux
IdentifiersCVE-2017-7308CWE-787 · Out-of-bounds Write

CVE-2017-7308 is a Linux kernel flaw in the AF_PACKET socket implementation, in packet_set_ring() in net/packet/af_packet.c. The privileged-area size validation for packet-ring block configuration mishandles signedness and does not correctly validate crafted block-size data. A local attacker can issue crafted packet-socket system calls that cause an integer signedness error and an ensuing out-of-bounds kernel write. Linux kernels through 4.10.6 are affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the kernel or otherwise cause local denial of service. An attacker holding CAP_NET_RAW can use the out-of-bounds write to corrupt kernel memory and potentially escalate privileges to kernel-level or root execution. In containerized deployments, CAP_NET_RAW combined with a vulnerable host kernel may make the flaw relevant to container-escape chains.

Mitigation

If you can’t patch tonight, do this now.

Until patched kernels can be deployed, restrict access to packet sockets and remove CAP_NET_RAW from untrusted users, containers, and workloads. Disable unprivileged user namespaces where operationally feasible, as they can enable attackers to obtain namespace-scoped network capabilities needed to reach AF_PACKET. Apply least-privilege container capability policies and prevent untrusted local code execution.

Remediation

Patch, then assume compromise.

Install a Linux kernel update containing the vendor backport or an upstream kernel version newer than 4.10.6. Distribution-specific kernel security updates that remediate CVE-2017-7308 should be applied, followed by a system reboot so the updated kernel is running.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2017-7308 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-7308 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-7308?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2017-7308, the earliest disclosed Mar 29, 2017.
Is there a patch for CVE-2017-7308?
Install a Linux kernel update containing the vendor backport or an upstream kernel version newer than 4.10.6. Distribution-specific kernel security updates that remediate CVE-2017-7308 should be applied, followed by a system reboot so the updated kernel is running.
What products are affected by CVE-2017-7308?
Linux Kernel.
How severe is CVE-2017-7308?
CVE-2017-7308 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 17.8% (97th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.