CVE-2017-9150 json
The do_check function in kernel/bpf/verifier.c in the Linux kernel before 4.11.1 does not make the allow_ptr_leaks value available for rest…
published 2017-05-22 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18088
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 69%
- public exploits
- 1
- Exploit-DB
Summary
The do_check function in kernel/bpf/verifier.c in the Linux kernel before 4.11.1 does not make the allow_ptr_leaks value available for restricting the output of the print_bpf_insn function, which allows local users to obtain sensitive address information via crafted bpf system calls.
Patch / fix
- linux Debian 14, Debian 13, Debian 12 4.9.30-1
debian advisories DEBIAN-CVE-2017-9150
- linux Ubuntu 16.04 LTS 4.4.0-87.110
- linux-aws Ubuntu 16.04 LTS 4.4.0-1026.35
- linux-gke Ubuntu 16.04 LTS 4.4.0-1022.22
- linux-hwe Ubuntu 16.04 LTS 4.10.0-32.36~16.04.1
- linux-raspi2 Ubuntu 16.04 LTS 4.4.0-1065.73
- linux-lts-xenial Ubuntu 14.04 LTS 4.4.0-87.110~14.04.1
- linux-snapdragon Ubuntu 16.04 LTS 4.4.0-1067.72
ubuntu advisories UBUNTU-CVE-2017-9150
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-rt SLE Real Time 12 SP2 4.4.74-7.10.1
- kernel-syms-rt SLE Real Time 12 SP2 4.4.74-7.10.1
- kernel-rt_debug SLE Real Time 12 SP2 4.4.74-7.10.1
- kernel-source-rt SLE Real Time 12 SP2 4.4.74-7.10.1
- kernel-syms SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 4.4.74-92.29.1
- kernel-source SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 4.4.74-92.29.1
- kernel-default SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +3 more 4.4.74-92.29.1
- kernel-obs-build SLE Software Development Kit 12 SP2 4.4.74-92.29.1
suse advisories SUSE-SU-2017:1990-1SUSE-SU-2017:1853-1
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-9150 updated cvss 3.3
kernel: eBPF verifier log leaks lower half of map pointer
-
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 MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmwarenot 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
Timeline
- First public exploit (EDB-42048)
- Published
Exploit prediction
1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-42048 Linux Kernel 4.11 - eBPF Verifier Log Leaks Lower Half of map Pointer dos, 2017-05-22
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:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
git.kernel.org
/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0d0e57697f162da4aa218b5feafe614fb666db07
issue-tracking, patch, third-party-advisory
-
github.com
/torvalds/linux/commit/0d0e57697f162da4aa218b5feafe614fb666db07
issue-tracking, patch, third-party-advisory
-
bugs.chromium.org
/p/project-zero/issues/detail?id=1251
issue-tracking, patch, third-party-advisory
-
exploit-db.com
/exploits/42048/
exploit
-
kernel.org
/pub/linux/kernel/v4.x/ChangeLog-4.11.1
release-notes, vendor-advisory
- source.android.com /security/bulletin/2017-09-01
-
securityfocus.com
/bid/98635
vdb-entry
Sources
- CVE List CVE-2017-9150
- NVD CVE-2017-9150
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.