Skip to content
Fencer Intel
medium 5.5

CVE-2017-17862 json

kernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores unreachable code, even though it would still be processed by JIT compilers.

published 8y ago modified 4mo ago also EUVD-2017-9009

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

kernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores unreachable code, even though it would still be processed by JIT compilers. This behavior, also considered an improper branch-pruning logic issue, could possibly be used by local users for denial of service.

Patch / fix

  • linux Debian 14, Debian 13, Debian 12 4.14.7-1

debian advisories DEBIAN-CVE-2017-17862

  • linux Ubuntu 16.04 LTS 4.4.0-119.143
  • linux-aws Ubuntu 14.04 LTS 4.4.0-1016.16
  • linux-aws Ubuntu 16.04 LTS 4.4.0-1054.63
  • linux-gcp Ubuntu 16.04 LTS 4.13.0-1006.9
  • linux-hwe Ubuntu 16.04 LTS 4.13.0-32.35~16.04.1
  • linux-kvm Ubuntu 16.04 LTS 4.4.0-1020.25
  • linux-oem Ubuntu 16.04 LTS 4.13.0-1015.16
  • linux-azure Ubuntu 16.04 LTS 4.13.0-1005.7

ubuntu advisories UBUNTU-CVE-2017-17862

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-syms SLES for SAP 12 SP3, SLES 12 SP3-LTSS, SLES 12 SP3-BCL +3 more 4.4.180-94.150.1
  • kernel-source SLES for SAP 12 SP3, SLES 12 SP3-LTSS, SLES 12 SP3-BCL +3 more 4.4.180-94.150.1
  • kernel-default SLES for SAP 12 SP3, SLES 12 SP3-LTSS, SLES 12 SP3-BCL +4 more 4.4.180-94.150.1
  • kgraft-patch-SLE12-SP3_Update_41 SLES for SAP 12 SP3, SLES 12 SP3-LTSS, OpenStack Cloud Crowbar 8 +2 more 1-4.3.1
  • kernel-rt SLE Real Time 12 SP3 4.4.120-3.8.1
  • kernel-syms-rt SLE Real Time 12 SP3 4.4.120-3.8.1
  • kernel-rt_debug SLE Real Time 12 SP3 4.4.120-3.8.1
  • kernel-source-rt SLE Real Time 12 SP3 4.4.120-3.8.1

suse advisories SUSE-SU-2021:3935-1SUSE-SU-2018:0986-1SUSE-SU-2018:0482-1SUSE-SU-2018:0416-1SUSE-SU-2018:0383-1

  • kernel-source openSUSE Tumbleweed 5.14.6-1.4
  • kernel-source openSUSE Tumbleweed 6.6.17-1.1

opensuse advisories openSUSE-SU-2024:10728-1openSUSE-SU-2024:13704-1

  • linux Arch Linux 4.14.11-1
  • linux-lts Arch Linux 4.9.74-1
  • linux-zen Arch Linux 4.14.11-1
  • linux-hardened Arch Linux 4.14.11.a-1

arch linux advisories AVG-552AVG-561AVG-571AVG-574

Is CVE-2017-17862 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-17862 updated cvss 4.7

kernel: Improper logic pruning in bpf/verifier.c

  • Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-core, kernel-tools, python3-perf, +17 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmware
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:N/I:N/A:C

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.