vciy

CVE-2017-1000410

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.

The Linux kernel version 3.3-rc1 and later is affected by a vulnerability lies in the processing of incoming L2CAP commands - ConfigRequest, and…

CVE-2017-10004103 of 4 sources documented this
29

rank 29 = 1 + 19 + 0 + 9 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.04217  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 10

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 29

How much of the world it touches

NVD CPE configurations

16 products in the CPE ranges  ·  without this subject the record ranks 20

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$129,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$129,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.04217 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.04217EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2021-04-14, 1971 days at 0.04, as of 2026-09-06. arc-rules@v1

Foresight · where to check next

Cisco AdaptiveminioCVE-2016-6415checkpoint CheckFortinet FortiOSCisco Catalyst1000410

This record is one instance of CWE-200, exposure of sensitive information to an unauthorized actor. The index holds 11146 prior instances of this class, 18 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

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 lossreceipt
Scored fromCVSS v3.0 · NVD's vectorreceipt
Weakness classCWE-200 Exposure of Sensitive Information to an Unauthorized Actorreceipt
Published consequencesCWE-200: Confidentiality: Read Application Data[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 4.15receipt
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: Nothing observed in held sources.

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

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.04217 · top 9% of all CVEsreceipt
Blast breadth9 products across 3 vendorsderived
Assigned bymitrereceipt
Recorded changes19 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesLinux kernel; Debian linux; Redhat enterprise linux desktop; and 6 morereceipt
Published rangeslinux kernel > 3.2 < 4.15; linux kernel 4.15; debian linux 8.0; debian linux 9.0receipt
Show all 16 published ranges
linux kernel > 3.2 < 4.15
linux kernel 4.15
debian linux 8.0
debian linux 9.0
redhat virtualization host 4.0
redhat enterprise linux desktop 6.0
redhat enterprise linux desktop 7.0
redhat enterprise linux server 6.0
redhat enterprise linux server 7.0
redhat enterprise linux server aus 7.6
redhat enterprise linux server eus 7.4
redhat enterprise linux server eus 7.6
redhat enterprise linux server tus 7.4
redhat enterprise linux server tus 7.6
redhat enterprise linux workstation 6.0
redhat enterprise linux workstation 7.0

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

The Linux kernel version 3.3-rc1 and later is affected by a vulnerability lies in the processing of incoming L2CAP commands - ConfigRequest, and ConfigResponse messages. This info leak is a result of uninitialized stack variables that may be returned to an attacker in their uninitialized state. By manipulating the code flows that precede the handling of these configuration messages, an attacker can also gain some control over which data will be held in the uninitialized stack variables. This can allow him to bypass KASLR, and stack canaries protection - as both pointers and stack canaries may be leaked in this manner. receipt

Read the rest of the CNA's description

Combining this vulnerability (for example) with the previously disclosed RCE vulnerability in L2CAP configuration parsing (CVE-2017-1000251) may allow an attacker to exploit the RCE against kernels which were built with the above mitigations. These are the specifics of this vulnerability: In the function l2cap_parse_conf_rsp and in the function l2cap_parse_conf_req the following variable is declared without initialization: struct l2cap_conf_efs efs; In addition, when parsing input configuration parameters in both of these functions, the switch case for handling EFS elements may skip the memcpy call that will write to the efs variable: ... case L2CAP_CONF_EFS: if (olen == sizeof(efs)) memcpy(&efs, (void *)val, olen); ... The olen in the above if is attacker controlled, and regardless of that if, in both of these functions the efs variable would eventually be added to the outgoing configuration request that is being built: l2cap_add_conf_opt(&ptr, L2CAP_CONF_EFS, sizeof(efs), (unsigned long) &efs); So by sending a configuration request, or response, that contains an L2CAP_CONF_EFS element, but with an element length that is not sizeof(efs) - the memcpy to the uninitialized efs variable can be avoided, and the uninitialized variable would be returned to the attacker (16 bytes).

NVD's analysis a second authority

severity
7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-200
affected versions
linux kernel > 3.2 < 4.15; linux kernel 4.15; debian linux 8.0; and 13 more, listed in full below

check it yourself seclists.org debian.org access.redhat.com access.redhat.com access.redhat.com help.ecostruxureit.com +7 morereceipt

Movement the material steps

14 Apr 20210.0288
7 Mar 20230.02238 · scoring model v2023.03.01
17 Mar 20250.02023 · scoring model v2025.03.14
15 Jun 20260.04252 · scoring model v2026.06.15
6 Sep 20260.04217
Show all 19 observations
14 Apr 20210.0288
4 Feb 20220.02686
7 Mar 20230.02238
30 Apr 20230.01887
8 May 20230.00824
9 Jun 20230.00592
3 Jul 20230.00590
12 Mar 20240.00416
17 Dec 20240.00226
17 Mar 20250.02023
29 Mar 20250.01908
30 Mar 20250.02023
23 Jun 20250.01922
15 Jun 20260.04252
14 Aug 20260.04217
23 Aug 20260.03874
30 Aug 20260.04217
5 Sep 20260.03874
6 Sep 20260.04217

19 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.04217Published2017-12-07Index as of2026-09-06

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

Published 2017-12-07 receipt · Index as of 2026-09-06 derived

The pattern, elsewhere

This record is one instance of CWE-200, exposure of sensitive information to an unauthorized actor. The index holds 11146 prior instances of this class, 18 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2020-3259 · Cisco Adaptive Security Appliance (ASA)…matches 8 of 8KEV listed · 2020receipt
CVE-2023-28432 · miniomatches 8 of 8KEV listed · 2023receipt
CVE-2016-6415matches 8 of 8KEV listed · 2016receipt
CVE-2024-24919 · checkpoint Check Point Quantum Gateway, Spark…matches 7 of 8KEV listed · 2024receipt
CVE-2025-68686 · Fortinet FortiOSmatches 7 of 8KEV listed · 2026receipt
CVE-2026-20133 · Cisco Catalyst SD-WAN Managermatches 7 of 8KEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

11146 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2017-1000410.

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.