{"id":"CVE-2017-17856","aliases":["DEBIAN-CVE-2017-17856","EUVD-2017-9003","GHSA-8r3h-6rgp-rrqm","MGASA-2018-0062","MGASA-2018-0063","MGASA-2018-0064","UBUNTU-CVE-2017-17856","openSUSE-SU-2024:10728-1","openSUSE-SU-2024:13704-1"],"status":"published","title":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of...","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-08","score":0.00393,"percentile":0.33752,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-119"],"published":"2017-12-23T04:00:00Z","modified":"2026-09-01T20:03:45Z","fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["4.14.7-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["4.14.7-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["4.14.7-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.7-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.7-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.7-1"}]}]},{"source":"osv","ecosystem":"Mageia:6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-userspace-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-vboxadditions","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.2-5.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.2-5.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.13-8.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"wireguard-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20171221-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-tmb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":26},{"source":"osv","ecosystem":"Mageia:6","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.14.10-1.mga6"}]}],"bundled":25},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.6-1.4"}]}],"bundled":119},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.17-1.1"}]}],"bundled":194}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://github.com/torvalds/linux/commit/a5ec6ae161d72f01411169a938fa5f8baea16e8f","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix"]},{"url":"http://www.openwall.com/lists/oss-security/2017/12/21/2","tags":["x_refsource_MISC","x_transferred","Mailing List","Third Party Advisory","advisory"]},{"url":"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a5ec6ae161d72f01411169a938fa5f8baea16e8f","tags":["x_refsource_MISC","x_transferred","Vendor Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-17856"},{"url":"https://github.com/advisories/GHSA-8r3h-6rgp-rrqm"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-17856","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2018-0062.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=22166","tags":["report"]},{"url":"https://kernelnewbies.org/Linux_4.10","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.11","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.12","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.13","tags":["web"]},{"url":"https://kernelnewbies.org/Linux_4.14","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.1","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.2","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.3","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.4","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.5","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.6","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.7","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.8","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.9","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.10","tags":["web"]},{"url":"https://www.wireguard.com/","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2018-0063.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=22268","tags":["report"]},{"url":"https://advisories.mageia.org/MGASA-2018-0064.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=22269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17856","tags":["report"]},{"url":"http://www.openwall.com/lists/oss-security/2017/12/23/2","tags":["report"]},{"url":"https://git.kernel.org/linus/a5ec6ae161d72f01411169a938fa5f8baea16e8f","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-17856","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2017-1000251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-16996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-13053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-8043","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-8087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-8822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-17133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-17666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-18808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-18812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-18813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3882","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-6974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-7221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-7222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-8564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-8912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-12351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-12352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-14331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-14386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-24586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-24587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-24588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-2732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-23133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-26708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-28971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-32606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-33909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-38166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-3695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-43976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-0886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-1973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-22942","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-24958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-2590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-26490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-28893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-29900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-29901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-29968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-34918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-3640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-40982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-41218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-41674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-42722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-4379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-44032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-44033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-44034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45919","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-45934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-0045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-1380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-20569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-20593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-2124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-31084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-3269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-39192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-39193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-46813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-4881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-5345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-6610","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2017-17856","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","status":"published","published":"2017-12-23T04:00:00Z","modified":"2024-08-05T21:06:49.094Z","updated_at":"2026-11-02T14:33:18.556155Z"}],"euvd":[{"id":"EUVD-2017-9003","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","status":"published","published":"2017-12-23T04:00:00Z","modified":"2024-08-05T21:06:49Z","updated_at":"2026-11-03T02:23:08.488418Z"}],"ghsa":[{"id":"GHSA-8r3h-6rgp-rrqm","title":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of...","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","status":"published","published":"2022-05-14T03:52:03Z","modified":"2023-02-03T05:00:46Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T14:52:51.467928Z"}],"nvd":[{"id":"CVE-2017-17856","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","status":"published","published":"2017-12-27T17:08:20.297Z","modified":"2026-06-17T01:11:46.913Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":7.2,"vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","level":"high","assessor":"primary"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T14:04:11.215487Z"}],"osv":[{"id":"CVE-2017-17856","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","status":"published","published":"2017-12-27T17:08:20.297Z","modified":"2026-04-16T06:20:49.818733468Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:04.853379Z"},{"id":"DEBIAN-CVE-2017-17856","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","status":"published","published":"2017-12-27T17:08:20.297Z","modified":"2026-09-01T20:03:45.919640978Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:29.100767Z"},{"id":"UBUNTU-CVE-2017-17856","description":"kernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the lack of stack-pointer alignment enforcement.","status":"withdrawn","published":"2017-12-27T17:08:00Z","modified":"2025-07-16T07:36:27.819916Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"},{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:14.977781Z"},{"id":"MGASA-2018-0062","title":"kernel update provides 4.14 series and fixes security vulnerabilities","description":"This kernel update provides an upgrade to the 4.14 longterm branch,\ncurrently based on 4.14.10. It also fixes at least the following\nsecurity issues:\n\nAn elevation of privilege vulnerability in the Broadcom wi-fi driver\n(CVE-2017-0786).\n\nUse-after-free vulnerability in the snd_pcm_info function in the ALSA\nsubsystem in the Linux kernel allows attackers to gain privileges via\nunspecified vectors (CVE-2017-0861).\n\nLinux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM)\nsupport is vulnerable to an incorrect debug exception(#DB) error. It\ncould occur while emulating a syscall instruction. A user/process\ninside guest could use this flaw to potentially escalate their\nprivileges inside guest. Linux guests are not affected.(CVE-2017-7518).\n\narch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested\nvirtualisation is used, does not properly traverse guest pagetable\nentries to resolve a guest virtual address, which allows L1 guest OS\nusers to execute arbitrary code on the host OS or cause a denial of\nservice (incorrect index during page walking, and host OS crash), aka\nan \"MMU potential stack buffer overrun\" (CVE-2017-12188).\n\nThe bio_map_user_iov and bio_unmap_user functions in block/bio.c in the\nLinux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O\nvector has small consecutive buffers belonging to the same page. The\nbio_add_pc_page function merges them into one, but the page reference\nis never dropped. This causes a memory leak and possible system lockup\n(exploitable against the host OS by a guest OS user, if a SCSI disk is\npassed through to a virtual machine) due to an out-of-memory condition\n(CVE-2017-12190).\n\nThe assoc_array_insert_into_terminal_node function in lib/assoc_array.c\nin the Linux kernel before 4.13.11 mishandles node splitting, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\npanic) via a crafted application, as demonstrated by the keyring key type,\nand key addition and link creation operations (CVE-2017-12193).\n\nWi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group\nTemporal Key (GTK) during the group key handshake, allowing an attacker\nwithin radio range to replay frames from access points to clients\n(CVE-2017-13080).\n\nThe sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel\nbefore 4.14 does not check whether the intended netns is used in a\npeel-off action, which allows local users to cause a denial of\nservice (use-after-free and system crash) or possibly have unspecified\nother impact via crafted system calls (CVE-2017-15115).\n\nRace condition in the ALSA subsystem in the Linux kernel before 4.13.8\nallows local users to cause a denial of service (use-after-free) or\npossibly have unspecified other impact via crafted /dev/snd/seq ioctl\ncalls, related to sound/core/seq/seq_clientmgr.c and \nsound/core/seq/seq_ports.c (CVE-2017-15265)\n\nThe KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of\nadd_key for a key that already exists but is uninstantiated, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\nsystem crash) or possibly have unspecified other impact via a crafted\nsystem call (CVE-2017-15299).\n\nThe XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux\nkernel before 4.13.11 allows local users to gain privileges or cause a\ndenial of service (use-after-free) via a crafted SO_RCVBUF setsockopt\nsystem call in conjunction with XFRM_MSG_GETPOLICY Netlink messages\n(CVE-2017-16939).\n\nThe walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel\nbefore 4.14.2 mishandles holes in hugetlb ranges, which allows local\nusers to obtain sensitive information from uninitialized kernel memory\nvia crafted use of the mincore() system call (CVE-2017-16994).\n\nThe check_alu_op function in kernel/bpf/verifier.c in the Linux kernel\nthrough 4.14.8 allows local users to cause a denial of service (memory\ncorruption) or possibly have unspecified other impact by leveraging\nincorrect sign extension (CVE-2017-16995).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging register truncation mishandling\n(CVE-2017-16996).\n\nThe KVM implementation in the Linux kernel through 4.14.7 allows attackers\nto obtain potentially sensitive information from kernel memory, aka a\nwrite_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c\nand include/trace/events/kvm.h (CVE-2017-17741).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging mishandling of 32-bit ALU ops\n(CVE-2017-17852).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging incorrect BPF_RSH signed bounds\ncalculations (CVE-2017-17853).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (integer overflow and memory\ncorruption) or possibly have unspecified other impact by leveraging\nunrestricted integer values for pointer arithmetic (CVE-2017-17854).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging improper use of pointers in\nplace of scalars (CVE-2017-17855).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly\nhave unspecified other impact by leveraging the lack of stack-pointer\nalignment enforcement (CVE-2017-17856).\n\nThe check_stack_boundary function in kernel/bpf/verifier.c in the Linux\nkernel through 4.14.8 allows local users to cause a denial of service\n(memory corruption) or possibly have unspecified other impact by\nleveraging mishandling of invalid variable stack read operations\n(CVE-2017-17857).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores\nunreachable code, even though it would still be processed by JIT\ncompilers. This behavior, also considered an improper branch-pruning\nlogic issue, could possibly be used by local users for denial of\nservice (CVE-2017-17862).\n\nkernel/bpf/verifier.c in the Linux kernel 4.9.x through 4.9.71 does not\ncheck the relationship between pointer values and the BPF stack, which\nallows local users to cause a denial of service (integer overflow or\ninvalid memory access) or possibly have unspecified other impact\n(CVE-2017-17863).\n\nkernel/bpf/verifier.c in the Linux kernel before 4.14 mishandles\nstates_equal comparisons between the pointer data type and the\nUNKNOWN_VALUE data type, which allows local users to obtain potentially\nsensitive address information, aka a \"pointer leak\" (CVE-2017-17864).\n\nThe timer_create syscall implementation in kernel/time/posix-timers.c\nin the Linux kernel before 4.14.8 doesn't properly validate the\nsigevent-\u003esigev_notify field, which leads to out-of-bounds access in\nthe show_timer function (called when /proc/$PID/timers is read).\nThis allows userspace applications to read arbitrary kernel memory\n(on a kernel built with CONFIG_POSIX_TIMERS and\nCONFIG_CHECKPOINT_RESTORE)(CVE-2017-18344).\n\nThe Linux Kernel 2.6.32 and later are affected by a denial of service,\nby flooding the diagnostic port 0x80 an exception can be triggered\nleading to a kernel panic (CVE-2017-1000407).\n\nThis update also adds support for WireGuard VPN.\n\nFor other changes in this update, read the referenced changelogs.\n","status":"published","published":"2018-01-06T00:53:31Z","modified":"2026-04-16T06:26:17.325590936Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2018-0063","title":"kernel-tmb update provides 4.14 series and fixes security vulnerabilities","description":"This kernel-tmb update provides an upgrade to the 4.14 longterm branch,\ncurrently based on 4.14.10. It also fixes at least the following\nsecurity issues:\n\nAn elevation of privilege vulnerability in the Broadcom wi-fi driver\n(CVE-2017-0786).\n\nUse-after-free vulnerability in the snd_pcm_info function in the ALSA\nsubsystem in the Linux kernel allows attackers to gain privileges via\nunspecified vectors (CVE-2017-0861).\n\nLinux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM)\nsupport is vulnerable to an incorrect debug exception(#DB) error. It\ncould occur while emulating a syscall instruction. A user/process\ninside guest could use this flaw to potentially escalate their\nprivileges inside guest. Linux guests are not affected.(CVE-2017-7518).\n\narch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested\nvirtualisation is used, does not properly traverse guest pagetable\nentries to resolve a guest virtual address, which allows L1 guest OS\nusers to execute arbitrary code on the host OS or cause a denial of\nservice (incorrect index during page walking, and host OS crash), aka\nan \"MMU potential stack buffer overrun\" (CVE-2017-12188).\n\nThe bio_map_user_iov and bio_unmap_user functions in block/bio.c in the\nLinux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O\nvector has small consecutive buffers belonging to the same page. The\nbio_add_pc_page function merges them into one, but the page reference\nis never dropped. This causes a memory leak and possible system lockup\n(exploitable against the host OS by a guest OS user, if a SCSI disk is\npassed through to a virtual machine) due to an out-of-memory condition\n(CVE-2017-12190).\n\nThe assoc_array_insert_into_terminal_node function in lib/assoc_array.c\nin the Linux kernel before 4.13.11 mishandles node splitting, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\npanic) via a crafted application, as demonstrated by the keyring key type,\nand key addition and link creation operations (CVE-2017-12193).\n\nWi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group\nTemporal Key (GTK) during the group key handshake, allowing an attacker\nwithin radio range to replay frames from access points to clients\n(CVE-2017-13080).\n\nThe sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel\nbefore 4.14 does not check whether the intended netns is used in a\npeel-off action, which allows local users to cause a denial of\nservice (use-after-free and system crash) or possibly have unspecified\nother impact via crafted system calls (CVE-2017-15115).\n\nRace condition in the ALSA subsystem in the Linux kernel before 4.13.8\nallows local users to cause a denial of service (use-after-free) or\npossibly have unspecified other impact via crafted /dev/snd/seq ioctl\ncalls, related to sound/core/seq/seq_clientmgr.c and \nsound/core/seq/seq_ports.c (CVE-2017-15265)\n\nThe KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of\nadd_key for a key that already exists but is uninstantiated, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\nsystem crash) or possibly have unspecified other impact via a crafted\nsystem call (CVE-2017-15299).\n\nThe XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux\nkernel before 4.13.11 allows local users to gain privileges or cause a\ndenial of service (use-after-free) via a crafted SO_RCVBUF setsockopt\nsystem call in conjunction with XFRM_MSG_GETPOLICY Netlink messages\n(CVE-2017-16939).\n\nThe walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel\nbefore 4.14.2 mishandles holes in hugetlb ranges, which allows local\nusers to obtain sensitive information from uninitialized kernel memory\nvia crafted use of the mincore() system call (CVE-2017-16994).\n\nThe check_alu_op function in kernel/bpf/verifier.c in the Linux kernel\nthrough 4.14.8 allows local users to cause a denial of service (memory\ncorruption) or possibly have unspecified other impact by leveraging\nincorrect sign extension (CVE-2017-16995).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging register truncation mishandling\n(CVE-2017-16996).\n\nThe KVM implementation in the Linux kernel through 4.14.7 allows attackers\nto obtain potentially sensitive information from kernel memory, aka a\nwrite_mmio stack-based out-of-bounds read, related to arch/x86/kvm/x86.c\nand include/trace/events/kvm.h (CVE-2017-17741).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging mishandling of 32-bit ALU ops\n(CVE-2017-17852).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging incorrect BPF_RSH signed bounds\ncalculations (CVE-2017-17853).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (integer overflow and memory\ncorruption) or possibly have unspecified other impact by leveraging\nunrestricted integer values for pointer arithmetic (CVE-2017-17854).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging improper use of pointers in\nplace of scalars (CVE-2017-17855).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly\nhave unspecified other impact by leveraging the lack of stack-pointer\nalignment enforcement (CVE-2017-17856).\n\nThe check_stack_boundary function in kernel/bpf/verifier.c in the Linux\nkernel through 4.14.8 allows local users to cause a denial of service\n(memory corruption) or possibly have unspecified other impact by\nleveraging mishandling of invalid variable stack read operations\n(CVE-2017-17857).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores\nunreachable code, even though it would still be processed by JIT\ncompilers. This behavior, also considered an improper branch-pruning\nlogic issue, could possibly be used by local users for denial of\nservice (CVE-2017-17862).\n\nkernel/bpf/verifier.c in the Linux kernel 4.9.x through 4.9.71 does not\ncheck the relationship between pointer values and the BPF stack, which\nallows local users to cause a denial of service (integer overflow or\ninvalid memory access) or possibly have unspecified other impact\n(CVE-2017-17863).\n\nkernel/bpf/verifier.c in the Linux kernel before 4.14 mishandles\nstates_equal comparisons between the pointer data type and the\nUNKNOWN_VALUE data type, which allows local users to obtain potentially\nsensitive address information, aka a \"pointer leak\" (CVE-2017-17864).\n\nThe timer_create syscall implementation in kernel/time/posix-timers.c\nin the Linux kernel before 4.14.8 doesn't properly validate the\nsigevent-\u003esigev_notify field, which leads to out-of-bounds access in\nthe show_timer function (called when /proc/$PID/timers is read).\nThis allows userspace applications to read arbitrary kernel memory\n(on a kernel built with CONFIG_POSIX_TIMERS and\nCONFIG_CHECKPOINT_RESTORE)(CVE-2017-18344).\n\nThe Linux Kernel 2.6.32 and later are affected by a denial of service,\nby flooding the diagnostic port 0x80 an exception can be triggered\nleading to a kernel panic (CVE-2017-1000407).\n\nThis update also adds support for WireGuard VPN.\n\nFor other changes in this update, read the referenced changelogs.\n","status":"published","published":"2018-01-06T00:53:31Z","modified":"2026-04-16T06:22:43.462881638Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2018-0064","title":"kernel-linus update provides 4.14 series and fixes security vulnerabilities","description":"This kernel-linus update provides an upgrade to the 4.14 longterm\nbranch, currently based on 4.14.10. It also fixes at least the\nfollowing security issues:\n\nAn elevation of privilege vulnerability in the Broadcom wi-fi driver\n(CVE-2017-0786).\n\nUse-after-free vulnerability in the snd_pcm_info function in the ALSA\nsubsystem in the Linux kernel allows attackers to gain privileges via\nunspecified vectors (CVE-2017-0861).\n\nLinux kernel built with the Kernel-based Virtual Machine(CONFIG_KVM)\nsupport is vulnerable to an incorrect debug exception(#DB) error. It\ncould occur while emulating a syscall instruction. A user/process\ninside guest could use this flaw to potentially escalate their\nprivileges inside guest. Linux guests are not affected.(CVE-2017-7518).\n\narch/x86/kvm/mmu.c in the Linux kernel through 4.13.5, when nested\nvirtualisation is used, does not properly traverse guest pagetable\nentries to resolve a guest virtual address, which allows L1 guest OS\nusers to execute arbitrary code on the host OS or cause a denial of\nservice (incorrect index during page walking, and host OS crash), aka\nan \"MMU potential stack buffer overrun\" (CVE-2017-12188).\n\nThe bio_map_user_iov and bio_unmap_user functions in block/bio.c in the\nLinux kernel before 4.13.8 do unbalanced refcounting when a SCSI I/O\nvector has small consecutive buffers belonging to the same page. The\nbio_add_pc_page function merges them into one, but the page reference\nis never dropped. This causes a memory leak and possible system lockup\n(exploitable against the host OS by a guest OS user, if a SCSI disk is\npassed through to a virtual machine) due to an out-of-memory condition\n(CVE-2017-12190).\n\nThe assoc_array_insert_into_terminal_node function in lib/assoc_array.c\nin the Linux kernel before 4.13.11 mishandles node splitting, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\npanic) via a crafted application, as demonstrated by the keyring key type,\nand key addition and link creation operations (CVE-2017-12193).\n\nWi-Fi Protected Access (WPA and WPA2) allows reinstallation of the Group\nTemporal Key (GTK) during the group key handshake, allowing an attacker\nwithin radio range to replay frames from access points to clients\n(CVE-2017-13080).\n\nThe sctp_do_peeloff function in net/sctp/socket.c in the Linux kernel\nbefore 4.14 does not check whether the intended netns is used in a\npeel-off action, which allows local users to cause a denial of\nservice (use-after-free and system crash) or possibly have unspecified\nother impact via crafted system calls (CVE-2017-15115).\n\nRace condition in the ALSA subsystem in the Linux kernel before 4.13.8\nallows local users to cause a denial of service (use-after-free) or\npossibly have unspecified other impact via crafted /dev/snd/seq ioctl\ncalls, related to sound/core/seq/seq_clientmgr.c and \nsound/core/seq/seq_ports.c (CVE-2017-15265)\n\nThe KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of\nadd_key for a key that already exists but is uninstantiated, which allows\nlocal users to cause a denial of service (NULL pointer dereference and\nsystem crash) or possibly have unspecified other impact via a crafted\nsystem call (CVE-2017-15299).\n\nThe XFRM dump policy implementation in net/xfrm/xfrm_user.c in the Linux\nkernel before 4.13.11 allows local users to gain privileges or cause a\ndenial of service (use-after-free) via a crafted SO_RCVBUF setsockopt\nsystem call in conjunction with XFRM_MSG_GETPOLICY Netlink messages\n(CVE-2017-16939).\n\nThe walk_hugetlb_range function in mm/pagewalk.c in the Linux kernel\nbefore 4.14.2 mishandles holes in hugetlb ranges, which allows local\nusers to obtain sensitive information from uninitialized kernel memory\nvia crafted use of the mincore() system call (CVE-2017-16994).\n\nThe check_alu_op function in kernel/bpf/verifier.c in the Linux kernel\nthrough 4.14.8 allows local users to cause a denial of service (memory\ncorruption) or possibly have unspecified other impact by leveraging\nincorrect sign extension (CVE-2017-16995).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging register truncation mishandling\n(CVE-2017-16996).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging mishandling of 32-bit ALU ops\n(CVE-2017-17852).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging incorrect BPF_RSH signed bounds\ncalculations (CVE-2017-17853).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (integer overflow and memory\ncorruption) or possibly have unspecified other impact by leveraging\nunrestricted integer values for pointer arithmetic (CVE-2017-17854).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly have\nunspecified other impact by leveraging improper use of pointers in\nplace of scalars (CVE-2017-17855).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 allows local\nusers to cause a denial of service (memory corruption) or possibly\nhave unspecified other impact by leveraging the lack of stack-pointer\nalignment enforcement (CVE-2017-17856).\n\nThe check_stack_boundary function in kernel/bpf/verifier.c in the Linux\nkernel through 4.14.8 allows local users to cause a denial of service\n(memory corruption) or possibly have unspecified other impact by\nleveraging mishandling of invalid variable stack read operations\n(CVE-2017-17857).\n\nkernel/bpf/verifier.c in the Linux kernel through 4.14.8 ignores\nunreachable code, even though it would still be processed by JIT\ncompilers. This behavior, also considered an improper branch-pruning\nlogic issue, could possibly be used by local users for denial of\nservice (CVE-2017-17862).\n\nkernel/bpf/verifier.c in the Linux kernel 4.9.x through 4.9.71 does not\ncheck the relationship between pointer values and the BPF stack, which\nallows local users to cause a denial of service (integer overflow or\ninvalid memory access) or possibly have unspecified other impact\n(CVE-2017-17863).\n\nkernel/bpf/verifier.c in the Linux kernel before 4.14 mishandles\nstates_equal comparisons between the pointer data type and the\nUNKNOWN_VALUE data type, which allows local users to obtain potentially\nsensitive address information, aka a \"pointer leak\" (CVE-2017-17864).\n\nThe timer_create syscall implementation in kernel/time/posix-timers.c\nin the Linux kernel before 4.14.8 doesn't properly validate the\nsigevent-\u003esigev_notify field, which leads to out-of-bounds access in\nthe show_timer function (called when /proc/$PID/timers is read).\nThis allows userspace applications to read arbitrary kernel memory\n(on a kernel built with CONFIG_POSIX_TIMERS and\nCONFIG_CHECKPOINT_RESTORE)(CVE-2017-18344).\n\nThe Linux Kernel 2.6.32 and later are affected by a denial of service,\nby flooding the diagnostic port 0x80 an exception can be triggered\nleading to a kernel panic (CVE-2017-1000407).\n\nFor other changes in this update, read the referenced changelogs.\n","status":"published","published":"2018-01-06T00:53:31Z","modified":"2026-04-16T06:22:49.505651352Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"openSUSE-SU-2024:10728-1","title":"kernel-devel-5.14.6-1.4 on GA media","description":"These are all security issues fixed in the kernel-devel-5.14.6-1.4 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:31:50.908235Z","updated_at":"2026-11-02T16:58:34.487567Z"},{"id":"openSUSE-SU-2024:13704-1","title":"kernel-devel-longterm-6.6.17-1.1 on GA media","description":"These are all security issues fixed in the kernel-devel-longterm-6.6.17-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:07:48.417979Z","updated_at":"2026-11-02T16:58:36.327643Z"}]}}