Skip to content

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 of service (memory corruption) or possibly have unspecified other impact by leveraging incorrect sign extension.

CVSS
7.8High
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
30.1%chance of exploitation in the next 30 daystop 2% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
27 Dec 2017analysed here 12 Nov 2026

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
local
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • linux:linux_kernel
  • debian:debian_linux
  • canonical:ubuntu_linux

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 4 on Exploit-DB · 1 Metasploit module · 15 GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 27 Dec 2017Published
  2. 16 Mar 2018First public exploit or proof of concept78 days (about 3 months) later
  3. 5 Aug 2024CVE record last updated2,335 days (about 6 years) later
  4. 12 Nov 2026Analysed by vulneraibility.com829 days (about 2 years) later

CVSS vector

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

MetricValueWhat it means
Attack vectorLocalLocal access required (shell, logged-in user).
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredLowThe attacker needs basic user privileges.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2017-16995 being exploited?

Not confirmed. CVE-2017-16995 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 30% probability of exploitation in the next 30 days.

How severe is CVE-2017-16995?

CVE-2017-16995 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2017-16995?

Yes. A fix has been recorded for CVE-2017-16995. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2017-16995 affect?

CVE-2017-16995 affects linux:linux_kernel, debian:debian_linux, canonical:ubuntu_linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

14 references in the CVE record, grouped by the tags the record gives them.

Advisories (5)

Exploits (3)

Other links (6)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com