CVE-2017-5123
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
8.8
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
- Record
CVE-2017-5123- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - CVSS 2.0
- 4.6 Medium
AV:L/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-20
- Updated
- 2026-11-02
CVE List No score
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
- Record
CVE-2017-5123- Updated
- 2026-11-02
EUVDEUVD-2017-14232 No score
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
- Record
EUVD-2017-14232- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-c436-43cf-26wj
8.8
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
- Record
GHSA-c436-43cf-26wj- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-20
- Updated
- 2026-11-02
OSV
8.8
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
- Record
CVE-2017-5123- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2017-5123
8.8
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
- Record
DEBIAN-CVE-2017-5123- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2017-5123
8.8
Insufficient data validation in waitid allowed an user to escape sandboxes on Linux.
- Record
UBUNTU-CVE-2017-5123- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10728-1 No score
kernel-devel-5.14.6-1.4 on GA media
These are all security issues fixed in the kernel-devel-5.14.6-1.4 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10728-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:13704-1 No score
kernel-devel-longterm-6.6.17-1.1 on GA media
These are all security issues fixed in the kernel-devel-longterm-6.6.17-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:13704-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
linuxDebian:12 |
before 4.13.4-2 | 4.13.4-2 |
linuxDebian:13 |
before 4.13.4-2 | 4.13.4-2 |
linuxDebian:14 |
before 4.13.4-2 | 4.13.4-2 |
kernel-sourceopenSUSE:Tumbleweed From an advisory covering 119 CVEs |
before 5.14.6-1.4 | 5.14.6-1.4 |
kernel-sourceopenSUSE:Tumbleweed From an advisory covering 194 CVEs |
before 6.6.17-1.1 | 6.6.17-1.1 |
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Exploit-DB | Linux Kernel 4.14.0-rc4+ - 'waitid()' Local Privilege Escalation | 2017-10-22 |
| PoC in GitHub | FloatingGuy/CVE-2017-5123 | 2017-10-31 |
| PoC in GitHub | 0x5068656e6f6c/CVE-2017-5123 | 2017-11-03 |
| Exploit-DB | Linux Kernel 4.13 (Ubuntu 17.10) - 'waitid()' SMEP/SMAP/Chrome Sandbox Privilege Escalation | 2017-11-06 |
| PoC in GitHub | Synacktiv-contrib/exploiting-cve-2017-5123 | 2018-03-01 |
| PoC in GitHub | teawater/CVE-2017-5123 | 2018-06-08 |
| PoC in GitHub | c3r34lk1ll3r/CVE-2017-5123 | 2020-05-08 |
| PoC in GitHub | h1bAna/CVE-2017-5123 | 2023-03-11 |
| PoC in GitHub | NabilBoudra/cve-2017-5123 | 2025-12-14 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, exploits, facts | ||
| affected | ||
| aliases | EUVD | |
| first indexed | CVE List, Exploit-DB, GitHub Advisories, NVD, OSV, PoC in GitHub |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-5123 is a high vulnerability (CVSS 8.8) in Linux Kernel, published October 12, 2017. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 3.74%, the 89th percentile. Fixed in linux 4.13.4-2.
References
crbug.com/772848
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=96ca579a1ecc943b75beba58bebb0356f6cc4b51
security.netapp.com/advisory/ntap-20211223-0003
nvd.nist.gov/vuln/detail/CVE-2017-5123
github.com/advisories/GHSA-c436-43cf-26wj
security-tracker.debian.org/tracker/CVE-2017-5123
Show 194 moreShow less
ubuntu.com/security/CVE-2017-5123
cve.org/CVERecord?id=CVE-2017-5123
suse.com/security/cve/CVE-2017-1000251
suse.com/security/cve/CVE-2017-12153
suse.com/security/cve/CVE-2017-13080
suse.com/security/cve/CVE-2017-14051
suse.com/security/cve/CVE-2017-15129
suse.com/security/cve/CVE-2017-15265
suse.com/security/cve/CVE-2017-16536
suse.com/security/cve/CVE-2017-16537
suse.com/security/cve/CVE-2017-16645
suse.com/security/cve/CVE-2017-16646
suse.com/security/cve/CVE-2017-16647
suse.com/security/cve/CVE-2017-16648
suse.com/security/cve/CVE-2017-16995
suse.com/security/cve/CVE-2017-16996
suse.com/security/cve/CVE-2017-17448
suse.com/security/cve/CVE-2017-17449
suse.com/security/cve/CVE-2017-17450
suse.com/security/cve/CVE-2017-17852
suse.com/security/cve/CVE-2017-17853
suse.com/security/cve/CVE-2017-17854
suse.com/security/cve/CVE-2017-17855
suse.com/security/cve/CVE-2017-17856
suse.com/security/cve/CVE-2017-17857
suse.com/security/cve/CVE-2017-17862
suse.com/security/cve/CVE-2017-5123
suse.com/security/cve/CVE-2017-5715
suse.com/security/cve/CVE-2017-5753
suse.com/security/cve/CVE-2017-5754
suse.com/security/cve/CVE-2017-7541
suse.com/security/cve/CVE-2017-7542
suse.com/security/cve/CVE-2017-8824
suse.com/security/cve/CVE-2017-8831
suse.com/security/cve/CVE-2018-1000004
suse.com/security/cve/CVE-2018-10322
suse.com/security/cve/CVE-2018-10323
suse.com/security/cve/CVE-2018-1068
suse.com/security/cve/CVE-2018-1118
suse.com/security/cve/CVE-2018-12232
suse.com/security/cve/CVE-2018-12714
suse.com/security/cve/CVE-2018-13053
suse.com/security/cve/CVE-2018-18710
suse.com/security/cve/CVE-2018-19824
suse.com/security/cve/CVE-2018-5332
suse.com/security/cve/CVE-2018-5333
suse.com/security/cve/CVE-2018-8043
suse.com/security/cve/CVE-2018-8087
suse.com/security/cve/CVE-2018-8822
suse.com/security/cve/CVE-2019-10207
suse.com/security/cve/CVE-2019-11477
suse.com/security/cve/CVE-2019-11478
suse.com/security/cve/CVE-2019-11479
suse.com/security/cve/CVE-2019-14615
suse.com/security/cve/CVE-2019-14814
suse.com/security/cve/CVE-2019-14896
suse.com/security/cve/CVE-2019-15030
suse.com/security/cve/CVE-2019-15031
suse.com/security/cve/CVE-2019-15098
suse.com/security/cve/CVE-2019-15099
suse.com/security/cve/CVE-2019-15290
suse.com/security/cve/CVE-2019-15504
suse.com/security/cve/CVE-2019-15902
suse.com/security/cve/CVE-2019-16231
suse.com/security/cve/CVE-2019-16232
suse.com/security/cve/CVE-2019-16234
suse.com/security/cve/CVE-2019-17133
suse.com/security/cve/CVE-2019-17666
suse.com/security/cve/CVE-2019-18808
suse.com/security/cve/CVE-2019-18812
suse.com/security/cve/CVE-2019-18813
suse.com/security/cve/CVE-2019-19252
suse.com/security/cve/CVE-2019-19332
suse.com/security/cve/CVE-2019-19338
suse.com/security/cve/CVE-2019-3016
suse.com/security/cve/CVE-2019-3846
suse.com/security/cve/CVE-2019-3882
suse.com/security/cve/CVE-2019-3887
suse.com/security/cve/CVE-2019-6974
suse.com/security/cve/CVE-2019-7221
suse.com/security/cve/CVE-2019-7222
suse.com/security/cve/CVE-2019-8564
suse.com/security/cve/CVE-2019-8912
suse.com/security/cve/CVE-2019-9500
suse.com/security/cve/CVE-2020-10135
suse.com/security/cve/CVE-2020-10766
suse.com/security/cve/CVE-2020-10767
suse.com/security/cve/CVE-2020-10768
suse.com/security/cve/CVE-2020-12351
suse.com/security/cve/CVE-2020-12352
suse.com/security/cve/CVE-2020-14331
suse.com/security/cve/CVE-2020-14386
suse.com/security/cve/CVE-2020-24586
suse.com/security/cve/CVE-2020-24587
suse.com/security/cve/CVE-2020-24588
suse.com/security/cve/CVE-2020-25639
suse.com/security/cve/CVE-2020-25656
suse.com/security/cve/CVE-2020-25668
suse.com/security/cve/CVE-2020-26141
suse.com/security/cve/CVE-2020-2732
suse.com/security/cve/CVE-2020-29660
suse.com/security/cve/CVE-2020-29661
suse.com/security/cve/CVE-2020-8648
suse.com/security/cve/CVE-2020-8694
suse.com/security/cve/CVE-2021-23133
suse.com/security/cve/CVE-2021-26708
suse.com/security/cve/CVE-2021-28971
suse.com/security/cve/CVE-2021-32606
suse.com/security/cve/CVE-2021-33909
suse.com/security/cve/CVE-2021-3483
suse.com/security/cve/CVE-2021-3489
suse.com/security/cve/CVE-2021-3490
suse.com/security/cve/CVE-2021-3491
suse.com/security/cve/CVE-2021-3640
suse.com/security/cve/CVE-2021-3653
suse.com/security/cve/CVE-2021-3656
suse.com/security/cve/CVE-2021-3744
suse.com/security/cve/CVE-2021-3753
suse.com/security/cve/CVE-2021-37576
suse.com/security/cve/CVE-2021-3759
suse.com/security/cve/CVE-2021-38166
suse.com/security/cve/CVE-2016-3695
suse.com/security/cve/CVE-2021-3542
suse.com/security/cve/CVE-2021-43976
suse.com/security/cve/CVE-2022-0185
suse.com/security/cve/CVE-2022-0330
suse.com/security/cve/CVE-2022-0847
suse.com/security/cve/CVE-2022-0886
suse.com/security/cve/CVE-2022-1462
suse.com/security/cve/CVE-2022-1516
suse.com/security/cve/CVE-2022-1679
suse.com/security/cve/CVE-2022-1729
suse.com/security/cve/CVE-2022-1852
suse.com/security/cve/CVE-2022-1966
suse.com/security/cve/CVE-2022-1972
suse.com/security/cve/CVE-2022-1973
suse.com/security/cve/CVE-2022-22942
suse.com/security/cve/CVE-2022-2308
suse.com/security/cve/CVE-2022-24958
suse.com/security/cve/CVE-2022-2588
suse.com/security/cve/CVE-2022-2590
suse.com/security/cve/CVE-2022-26490
suse.com/security/cve/CVE-2022-28388
suse.com/security/cve/CVE-2022-28389
suse.com/security/cve/CVE-2022-28390
suse.com/security/cve/CVE-2022-28893
suse.com/security/cve/CVE-2022-29900
suse.com/security/cve/CVE-2022-29901
suse.com/security/cve/CVE-2022-29968
suse.com/security/cve/CVE-2022-3424
suse.com/security/cve/CVE-2022-34918
suse.com/security/cve/CVE-2022-3628
suse.com/security/cve/CVE-2022-3640
suse.com/security/cve/CVE-2022-40982
suse.com/security/cve/CVE-2022-41218
suse.com/security/cve/CVE-2022-41674
suse.com/security/cve/CVE-2022-42719
suse.com/security/cve/CVE-2022-42720
suse.com/security/cve/CVE-2022-42721
suse.com/security/cve/CVE-2022-42722
suse.com/security/cve/CVE-2022-4379
suse.com/security/cve/CVE-2022-44032
suse.com/security/cve/CVE-2022-44033
suse.com/security/cve/CVE-2022-44034
suse.com/security/cve/CVE-2022-45884
suse.com/security/cve/CVE-2022-45885
suse.com/security/cve/CVE-2022-45886
suse.com/security/cve/CVE-2022-45887
suse.com/security/cve/CVE-2022-45888
suse.com/security/cve/CVE-2022-45919
suse.com/security/cve/CVE-2022-45934
suse.com/security/cve/CVE-2023-0045
suse.com/security/cve/CVE-2023-1076
suse.com/security/cve/CVE-2023-1078
suse.com/security/cve/CVE-2023-1192
suse.com/security/cve/CVE-2023-1380
suse.com/security/cve/CVE-2023-20569
suse.com/security/cve/CVE-2023-20593
suse.com/security/cve/CVE-2023-2124
suse.com/security/cve/CVE-2023-31084
suse.com/security/cve/CVE-2023-3141
suse.com/security/cve/CVE-2023-3269
suse.com/security/cve/CVE-2023-39192
suse.com/security/cve/CVE-2023-39193
suse.com/security/cve/CVE-2023-4128
suse.com/security/cve/CVE-2023-4134
suse.com/security/cve/CVE-2023-4194
suse.com/security/cve/CVE-2023-42753
suse.com/security/cve/CVE-2023-42754
suse.com/security/cve/CVE-2023-42756
suse.com/security/cve/CVE-2023-4623
suse.com/security/cve/CVE-2023-46813
suse.com/security/cve/CVE-2023-4881
suse.com/security/cve/CVE-2023-5345
Left out here: 2 references. The JSON record has them.