Home/CVE/The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial
CVE

CVE-2017-16995

The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial

The check_alu_op function in kernel/bpf/verifier.c in the Linux kernel through 4.4 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.

HIGH · CVSS 7.8 EPSS 0.84048
Act now
  • EPSS ≥ 0.50 - high probability of exploitation in the next 30 days
  • EPSS percentile: top 1% of all CVEs by exploitation likelihood
  • Reliable Metasploit module available (rank: Great) - weaponised exploit code
  • Public exploit or PoC is available
  • CVSS base score ≥ 7.0
Sigma rules0 YARA rules0
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2017-16995, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

ATT&CK techniques

1

Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.

▤ Build a SIEM detection for these techniques

Affected Products & Versions

4
linux kernel>= 4.9 and < 4.9.72
linux kernel>= 4.10 and < 4.14.9
debian linuxall versions

Affected Packages

40
Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Ubuntu:14.04:LTS linux fixed in 3.11.0-12.19
Ubuntu:14.04:LTS linux-aws fixed in 4.4.0-1016.16
Ubuntu:14.04:LTS linux-azure fixed in 4.15.0-1023.24~14.04.1
Ubuntu:14.04:LTS linux-lts-xenial fixed in 4.4.0-119.143~14.04.1
Ubuntu:16.04:LTS linux fixed in 4.4.0-119.143
Ubuntu:16.04:LTS linux-aws fixed in 4.4.0-1054.63
Ubuntu:16.04:LTS linux-aws-hwe fixed in 4.15.0-1030.31~16.04.1
Ubuntu:16.04:LTS linux-azure fixed in 4.13.0-1005.7
Ubuntu:16.04:LTS linux-euclid fixed in 4.4.0-9026.28
Ubuntu:16.04:LTS linux-gcp fixed in 4.13.0-1006.9
Ubuntu:16.04:LTS linux-hwe fixed in 4.13.0-32.35~16.04.1
Ubuntu:16.04:LTS linux-kvm fixed in 4.4.0-1020.25
Ubuntu:16.04:LTS linux-oem fixed in 4.13.0-1015.16
Ubuntu:16.04:LTS linux-oracle fixed in 4.15.0-1007.9~16.04.1
Ubuntu:16.04:LTS linux-raspi2 fixed in 4.4.0-1086.94
Ubuntu:16.04:LTS linux-snapdragon fixed in 4.4.0-1088.93
Ubuntu:18.04:LTS linux fixed in 4.13.0-25.29
Ubuntu:18.04:LTS linux-aws fixed in 4.15.0-1001.1
Ubuntu:18.04:LTS linux-aws-5.4 fixed in 5.4.0-1018.18~18.04.1
Ubuntu:18.04:LTS linux-azure fixed in 4.15.0-1002.2
Ubuntu:18.04:LTS linux-azure-4.15 fixed in 4.15.0-1082.92
Ubuntu:18.04:LTS linux-azure-5.4 fixed in 5.4.0-1020.20~18.04.1
Ubuntu:18.04:LTS linux-gcp fixed in 4.15.0-1001.1
Ubuntu:18.04:LTS linux-gcp-4.15 fixed in 4.15.0-1071.81
Ubuntu:18.04:LTS linux-gcp-5.4 fixed in 5.4.0-1019.19~18.04.2
Ubuntu:18.04:LTS linux-hwe-5.4 fixed in 5.4.0-37.41~18.04.1
Ubuntu:18.04:LTS linux-hwe-edge fixed in 5.0.0-15.16~18.04.1
Ubuntu:18.04:LTS linux-ibm-5.4 fixed in 5.4.0-1010.11~18.04.2
Ubuntu:18.04:LTS linux-kvm fixed in 4.15.0-1002.2
Ubuntu:18.04:LTS linux-oem fixed in 4.15.0-1002.3
Ubuntu:18.04:LTS linux-oracle fixed in 4.15.0-1007.9
Ubuntu:18.04:LTS linux-oracle-5.4 fixed in 5.4.0-1019.19~18.04.1
Ubuntu:18.04:LTS linux-raspi-5.4 fixed in 5.4.0-1013.13~18.04.1
Ubuntu:18.04:LTS linux-raspi2 fixed in 4.15.0-1006.7
Ubuntu:20.04:LTS linux fixed in 5.4.0-9.12
Ubuntu:20.04:LTS linux-aws fixed in 5.4.0-1005.5
Ubuntu:20.04:LTS linux-aws-5.15 fixed in 5.15.0-1014.18~20.04.1
Ubuntu:20.04:LTS linux-azure fixed in 5.4.0-1006.6
Ubuntu:20.04:LTS linux-azure-5.15 fixed in 5.15.0-1007.8~20.04.1
Ubuntu:20.04:LTS linux-azure-fde
📦

Fixed versions by distribution

14
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15kernel-azure-base fixed in 0:4.12.14-8.30.1
suse sle15kernel-default fixed in 0:4.12.14-195.1
suse sle15kernel-default-base fixed in 0:4.12.14-195.1
suse sle15kernel-default-extra fixed in 0:4.12.14-23.1
suse sle15kernel-default-man fixed in 0:4.12.14-197.40.1
suse sle15kernel-docs fixed in 0:4.12.14-195.1
suse sle15kernel-macros fixed in 0:4.12.14-23.1
suse sle15kernel-obs-build fixed in 0:4.12.14-23.1
suse sle15kernel-source fixed in 0:4.12.14-23.1
suse sle15kernel-source-azure fixed in 0:4.12.14-5.47.1
suse sle15kernel-syms fixed in 0:4.12.14-195.1
suse sle15kernel-vanilla-base fixed in 0:4.12.14-23.1
suse sle15kernel-zfcpdump fixed in 0:4.12.14-195.1
suse sle15reiserfs-kmp-default fixed in 0:4.12.14-23.1

Metasploit Modules

1
Weaponised exploit modules in the Metasploit Framework. Rank is Metasploit’s reliability rating - Excellent/Great/Good means dependable, real-world exploit code (a strong “act now” signal), not a fragile PoC.

Scoring & Timeline

7.8
HIGH · CVSS v3.1 · [email protected]
View on NVD
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
Published to NVD27 Dec 2017 · 05:08 PM
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Vendor Advisories

8
suse-csafopenSUSE-SU-2024:10728-1
suse-csafopenSUSE-SU-2024:13704-1
SOC and Response
CVE triage
Stack monitoring
Am I affected
IOC triage
KEV catalog
Daily brief
Change tracking
Detection Engineering
Coverage workspace
Detection coverage
Coverage check
Telemetry ceiling
SIEM query builder
Sigma rules
SIEM rules
YARA rules
Network rules
D3FEND
Threat Hunting
Threat actors
ATT&CK techniques
Attack paths
Indicators
Atomic tests
Red Team and Pentest
Exploitability triage
Recon pack
Attack paths
CAPEC patterns
Adversary emulation
Compliance and GRC
Framework mapping
Control assessment
Audit view
Coverage report
Atlas Search Threat actors Techniques Tools & malware CWE CAPEC KEV catalog Package vulns TAXII feed Data sources
About All capabilities Pricing API docs Live statistics Live status Privacy policy Terms of service
threatengine.sh