Skip to content
Noroxi
NVD / CVE Program· CNA mitre

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 91.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: linux (Debian:12) 4.14.7-1; linux (Debian:8) 3.16.51-3+deb8u1; linux (Debian:9) 4.9.65-3+deb9u1.

Low priority for now. Upgrade to linux (Debian:12) 4.14.7-1; linux (Debian:8) 3.16.51-3+deb8u1; linux (Debian:9) 4.9.65-3+deb9u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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. 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).

HighCVSS 7.5 · v3.0—No exploit Fix available
Published
Dec 7, 2017
Updated
Jun 16, 2026
EPSS
4.2% · 91th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2017-1000410

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux
redhatvirtualization host
redhatenterprise linux desktop
redhatenterprise linux server
redhatenterprise linux server aus
redhatenterprise linux server eus
redhatenterprise linux server tus
redhatenterprise linux workstation

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux8.0
  • debian debian linux9.0
  • linux linux kernelafter 3.2 · before 4.15
  • linux linux kernel4.15
  • redhat enterprise linux desktop6.0
  • redhat enterprise linux desktop7.0
  • redhat enterprise linux server6.0
  • redhat enterprise linux server7.0
  • redhat enterprise linux server aus7.6
  • redhat enterprise linux server eus7.4
  • redhat enterprise linux server eus7.6
  • redhat enterprise linux server tus7.4
  • redhat enterprise linux server tus7.6
  • redhat enterprise linux workstation6.0
  • redhat enterprise linux workstation7.0
  • redhat virtualization host4.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 4.14.7-14.14.7-1
Debian:8linuxbefore 3.16.51-3+deb8u13.16.51-3+deb8u1
Debian:9linuxbefore 4.9.65-3+deb9u14.9.65-3+deb9u1
Red Hat:enterprise_linux:6::clientkernelbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-abi-whitelistsbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-debugbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-debug-debuginfobefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-debug-develbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-debuginfobefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-debuginfo-common-i686before 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-debuginfo-common-x86_64before 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-develbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-docbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-firmwarebefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientkernel-headersbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientperfbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientperf-debuginfobefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientpython-perfbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::clientpython-perf-debuginfobefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::serverkernel-bootwrapperbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::serverkernel-debuginfo-common-ppc64before 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::serverkernel-debuginfo-common-s390xbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::serverkernel-kdumpbefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6
Red Hat:enterprise_linux:6::serverkernel-kdump-debuginfobefore 0:2.6.32-696.28.1.el60:2.6.32-696.28.1.el6

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2017-17449Dec 6, 2017 · The __netlink_deliver_tap_skb function in net/netlink/af_netlink.c in the Linux kernel through 4.14.4, when CONFIG_NLMON is enabled, does no
    18Monitor
  • ← EarlierCVE-2017-17450Dec 6, 2017 · net/netfilter/xt_osf.c in the Linux kernel through 4.14.4 does not require the CAP_NET_ADMIN capability for add_callback and remove_callback
    31Monitor
  • Later →CVE-2017-1000407Dec 11, 2017 · The Linux Kernel 2.6.32 and later are affected by a denial of service, by flooding the diagnostic port 0x80 an exception can be triggered le
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:linux4.14.7-1 · Debian:12Package registry (OSV)
red hat:kernel0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-abi-whitelists0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-alt0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-bootwrapper0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-debug0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-debug-devel0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-debuginfo0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-debuginfo-common-s390x0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:kernel-devel0:4.14.0-49.el7a · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
suse:kernel-default4.4.103-6.33.1 · SUSE:Linux Enterprise Desktop 12 SP3Package registry (OSV)
suse:kernel-docs4.4.103-6.33.1 · SUSE:Linux Enterprise Software Development Kit 12 SP3Package registry (OSV)
suse:kernel-obs-build4.4.103-6.33.1 · SUSE:Linux Enterprise Software Development Kit 12 SP3Package registry (OSV)
suse:kernel-rt4.4.104-24.1 · SUSE:Linux Enterprise Real Time 12 SP2Package registry (OSV)
suse:kernel-rt_debug4.4.104-24.1 · SUSE:Linux Enterprise Real Time 12 SP2Package registry (OSV)
suse:kernel-source4.4.103-6.33.1 · SUSE:Linux Enterprise Desktop 12 SP3Package registry (OSV)
suse:kernel-source-rt4.4.104-24.1 · SUSE:Linux Enterprise Real Time 12 SP2Package registry (OSV)
suse:kernel-syms4.4.103-6.33.1 · SUSE:Linux Enterprise Desktop 12 SP3Package registry (OSV)
suse:kernel-syms-rt4.4.104-24.1 · SUSE:Linux Enterprise Real Time 12 SP2Package registry (OSV)
suse:kgraft-patch-SLE12-SP2_Update_161-3.3.1 · SUSE:Linux Enterprise Live Patching 12Package registry (OSV)
suse:kgraft-patch-SLE12-SP3_Update_61-4.3.1 · SUSE:Linux Enterprise Live Patching 12 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records