Linux KernelOperating system · Linux
CVE-2017-1000111
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLinux kernel: heap out-of-bounds in AF_PACKET sockets. This new issue is analogous to previously disclosed CVE-2016-8655. In both cases, a socket option that changes socket state may race with safety checks in packet_set_ring. Previously with PACKET_VERSION. This time with PACKET_RESERVE. The solution is similar: lock the socket for the update. This issue may be exploitable, we did not investigate further. As this issue affects PF_PACKET sockets, it requires CAP_NET_RAW in the process namespace. But note that with user namespaces enabled, any process can create a namespace in which it has CAP_NET_RAW.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHeap out-of-bounds vulnerability in Linux kernel's AF_PACKET implementation caused by a race condition between the PACKET_RESERVE socket option and safety checks in packet_set_ring. An attacker with CAP_NET_RAW (including via user namespaces) can exploit this to achieve arbitrary kernel memory read/write. The fix requires locking the socket during the state update, similar to the prior CVE-2016-8655 patch.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 2.6.27, < 3.2.92>= 3.3, < 3.10.108>= 3.11, < 3.16.47>= 3.17, < 3.18.65>= 3.19, < 4.1.44>= 4.2, < 4.4.82>= 4.5, < 4.9.43>= 4.10, < 4.12.7
Enterprise LinuxOperating system
= 5.0= 6.0= 7.0
Enterprise Linux DesktopOperating system
= 6.0= 7.0
Enterprise Linux ServerOperating system
= 6.0= 7.0
Enterprise Linux Server AusOperating system
= 7.4= 7.6
Enterprise Linux Server EusOperating system
= 7.4= 7.5= 7.6
Enterprise Linux Server TusOperating system
= 7.4= 7.6
Enterprise Linux WorkstationOperating system
= 6.0= 7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify kernel versionRun 'uname -r' or check /proc/version to obtain the running kernel versionAffected if The kernel version falls within any of these ranges: >= 2.6.27 and < 3.2.92; >= 3.3 and < 3.10.108; >= 3.11 and < 3.16.47; >= 3.17 and < 3.18.65; >= 3.19 and < 4.1.44; >= 4.2 and < 4.4.82; >= 4.5 and < 4.9.43; >= 4.10 and < 4.12.7
-
Verify AF_PACKET socket supportCheck if the kernel has AF_PACKET support enabled. This may be a built-in config (CONFIG_PACKET) or a loaded module. Check /boot/config-$(uname -r) or /proc/config.gz for CONFIG_PACKET=y or CONFIG_PACKET=m, and verify the module status if built as modular.Affected if AF_PACKET (CONFIG_PACKET) is compiled into the kernel or loaded as a module, making packet sockets available
-
Detect active packet socket usageSearch for processes using AF_PACKET sockets. Use 'ss -ax' or 'netstat -ax' and look for state 'UNCONN' or 'LISTEN' on protocol 'packet', or inspect /proc/net/packet to list active packet sockets.Affected if Any process has created a packet socket (AF_PACKET family), which enables the vulnerable code path in packet_set_ring
-
Identify CAP_NET_RAW capability holdersCheck which users or processes can exercise CAP_NET_RAW. Use 'getcap -r /' to find programs with capabilities, or review /proc/$(pid)/status for each packet socket holder to see if they possess CAP_NET_RAW.Affected if Any untrusted user or container possesses CAP_NET_RAW capability, which is required to trigger the race condition via PACKET_RESERVE socket option
-
Check for user namespace usageInspect whether user namespaces are in use on the system. Look for processes with /proc/$(pid)/ns/user entries, or check if container runtimes (Docker, etc.) are active, as the CVE notes exploitation is possible via user namespaces.Affected if User namespaces are enabled or containers are in use, allowing local privilege escalation via this vulnerability even from seemingly sandboxed environments
The system is affected if the kernel version is within any of the listed vulnerable ranges AND AF_PACKET is available AND an attacker can obtain CAP_NET_RAW capability (including via user namespaces) to trigger the race condition in packet_set_ring.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.2.923.10.1083.16.47
Apply the kernel patch that adds proper socket locking around the PACKET_RESERVE update in packet_set_ring, or upgrade to a patched kernel version.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000111 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1000111 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data