vciy

CVE-2016-7117

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Use-after-free vulnerability in the __sys_recvmmsg function in net/socket.c in the Linux kernel before 4.5.2 allows remote attackers to execute…

CVE-2016-71173 of 4 sources documented this
53

rank 53 = 19 + 25 + 1 + 8 + 0

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.23558  ·  without this subject the record ranks 34

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 28

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-01-20  ·  without this subject the record ranks 52

How much of the world it touches

NVD CPE configurations

12 products in the CPE ranges  ·  without this subject the record ranks 45

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 53

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.18Mover the next 30 days, if this record is yours
Movement+$119,000on 2026-03-30, the last material move, 5 months before this reading
Basisassumeda published average, not your estate

$1.18M = $4.99M incident cost x 1 exposure x 0.23558 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.23558EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-05-30, 101 days at 0.24, as of 2026-09-08. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-19receipt
Published consequencesMITRE publishes no common consequences for this weakness.[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchkernel 3.10.102; kernel 3.12.59; kernel 3.14.67; kernel 3.16.35; kernel 3.18.37; kernel 3.2.80receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Proof-of-concept published · 1 public repository, 2016-10-14.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 1 public repository2016-10-14receipt
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.23558 · top 2% of all CVEsreceipt
Blast breadth3 products across 3 vendorsderived
Assigned bygoogle_androidreceipt
Recorded changes24 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesLinux kernel; Debian linux; Canonical ubuntu linuxreceipt
Published rangesdebian linux 7.0; linux kernel >= 2.6.33 < 3.2.80; linux kernel >= 3.3 < 3.4.113; linux kernel >= 3.5 < 3.10.102receipt
Show all 12 published ranges
debian linux 7.0
linux kernel >= 2.6.33 < 3.2.80
linux kernel >= 3.3 < 3.4.113
linux kernel >= 3.5 < 3.10.102
linux kernel >= 3.11 < 3.12.59
linux kernel >= 3.13 < 3.14.67
linux kernel >= 3.15 < 3.16.35
linux kernel >= 3.17 < 3.18.37
linux kernel >= 3.19 < 4.1.28
linux kernel >= 4.2.0 < 4.4.8
linux kernel >= 4.5.0 < 4.5.2
canonical ubuntu linux 16.04

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Use-after-free vulnerability in the __sys_recvmmsg function in net/socket.c in the Linux kernel before 4.5.2 allows remote attackers to execute arbitrary code via vectors involving a recvmmsg system call that is mishandled during error processing. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-19
affected versions
debian linux 7.0; linux kernel >= 2.6.33 < 3.2.80; linux kernel >= 3.3 < 3.4.113; and 9 more, listed in full below

check it yourself rhn.redhat.com security-tracker.debian.org source.android.com rhn.redhat.com rhn.redhat.com rhn.redhat.com +14 morereceipt

Dated events

2023-03-07EPSS moved 0.11 to 0.042026-06-15EPSS moved 0.15 to 0.24

Movement the material steps

4 Feb 20220.10938
7 Mar 20230.03935 · crossed 0.10 · scoring model v2023.03.01
17 Mar 20250.12777 · crossed 0.10 · scoring model v2025.03.14
16 Aug 20250.04788 · crossed 0.10
30 Mar 20260.10558 · crossed 0.10
15 Jun 20260.24299 · scoring model v2026.06.15
8 Sep 20260.23558
Show all 21 observations
4 Feb 20220.10938
7 Mar 20230.03935
8 May 20230.03811
9 Nov 20240.03897
17 Dec 20240.07687
17 Mar 20250.12777
19 Mar 20250.18322
20 Mar 20250.12777
27 Mar 20250.18322
28 Mar 20250.12777
29 Mar 20250.18322
30 Mar 20250.12777
16 Aug 20250.04788
18 Jan 20260.04913
20 Jan 20260.08385
28 Jan 20260.08181
30 Mar 20260.10558
30 May 20260.13687
5 Jun 20260.14755
15 Jun 20260.24299
8 Sep 20260.23558

21 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.23558Published2016-10-10Public PoC2016-10-14Index as of2026-09-08

The record had been public for 9 years, 10 months when this index was last written.

Published 2016-10-10 receipt · Public PoC 2016-10-14 receipt · Index as of 2026-09-08 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2016-7117.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.