Menu

Star on GitHub · 3.2k

CVE-2017-17864

3.3 · LOW

kernel/bpf/verifier.c in the Linux kernel through 4.14.8 mishandles states_equal comparisons between the pointer data type and the UNKNOWN_VALUE data type, which allows local users to obtain potent…

Published Dec 27, 2017CWE-200EPSS 0.40%

Overview

CVE-2017-17864 is a low-severity vulnerability. It was published on December 27, 2017 and has a CVSS 3.0 base score of 3.3 (LOW).

This vulnerability has a CVSS 3.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

kernel/bpf/verifier.c in the Linux kernel through 4.14.8 mishandles states_equal comparisons between the pointer data type and the UNKNOWN_VALUE data type, which allows local users to obtain potentially sensitive address information, aka a "pointer leak."

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2017-17864?

CVE-2017-17864 is a low-severity vulnerability. It was published on December 27, 2017 and has a CVSS 3.0 base score of 3.3 (LOW).

How severe is CVE-2017-17864?

This vulnerability has a CVSS 3.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2017-17864?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-17864?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-17864 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2017

View all