{"id":"CVE-2017-1000255","aliases":["DEBIAN-CVE-2017-1000255","EUVD-2017-1516","GHSA-7w7v-hmqg-8956","RHSA-2018:0654","UBUNTU-CVE-2017-1000255","USN-3443-2"],"status":"published","title":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame...","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","severity":{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.00382,"percentile":0.32445,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-787"],"published":"2017-10-09T00:00:00Z","modified":"2026-09-01T20:03:40Z","fixes":[{"ecosystem":"Debian:12","package":"linux","fixed_in":["4.13.4-2"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["4.13.4-2"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["4.13.4-2"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","fixed_in":["4.10.0-37.41~16.04.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.4-2"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.4-2"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.13.4-2"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-abi-whitelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-alt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-bootwrapper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-debug-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-debuginfo-common-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-debuginfo-common-ppc64le","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-debuginfo-common-s390x","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-kdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-kdump-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-kdump-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-tools-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"python-perf-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:4.14.0-49.el7a"}]}],"bundled":14},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.0-37.41~16.04.1"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.0-37.41~16.04.1"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1"],"bundled":2}],"products":[{"vendor":"linux","product":"linux_kernel"}],"references":[{"url":"https://access.redhat.com/errata/RHSA-2018:0654","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-1000255","tags":["x_refsource_MISC","x_transferred","Issue Tracking","Third Party Advisory","advisory","report"]},{"url":"http://www.securityfocus.com/bid/101264","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000255","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-7w7v-hmqg-8956"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-1000255","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.5_Release_Notes/index.html","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1473209","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1495089","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1498016","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1498067","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1501794","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1519160","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1519778","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1519780","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1519781","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1525762","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1525768","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1531174","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1535315","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1544612","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2018/rhsa-2018_0654.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-5753","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-5753","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-5753","tags":["advisory"]},{"url":"https://access.redhat.com/security/vulnerabilities/speculativeexecution","tags":["article"]},{"url":"https://googleprojectzero.blogspot.com/2018/01/reading-privileged-memory-with-side.html","tags":["article"]},{"url":"https://meltdownattack.com","tags":["article"]},{"url":"https://spectreattack.com/","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-11473","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-11473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-11473","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-12190","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-12190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-12190","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-12192","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1493435","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-12192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-12192","tags":["advisory"]},{"url":"http://seclists.org/oss-sec/2017/q4/63","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-15129","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-15129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-15129","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-15299","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-15299","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-15299","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-15306","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1510399","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-15306","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-15306","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-16939","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1517220","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-16939","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16939","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-17448","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-17448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-17448","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-17449","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-17449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-17449","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-1000255","tags":["advisory","report"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-1000410","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-1000410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000410","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-6927","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-6927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-6927","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1000004","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1000004","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000004","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2017-1000255","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3443-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3443-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3487-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2017-14106","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2017-1000255","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","status":"published","published":"2017-10-30T20:00:00Z","modified":"2024-08-05T22:00:39.695Z","updated_at":"2026-11-02T14:33:20.843976Z"}],"euvd":[{"id":"EUVD-2017-1516","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","status":"published","published":"2017-10-30T20:00:00Z","modified":"2024-08-05T22:00:39Z","updated_at":"2026-11-03T02:23:03.593375Z"}],"ghsa":[{"id":"GHSA-7w7v-hmqg-8956","title":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame...","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","status":"published","published":"2022-05-14T03:32:29Z","modified":"2023-02-02T05:08:03Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T14:52:39.182178Z"}],"nvd":[{"id":"CVE-2017-1000255","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","status":"published","published":"2017-10-30T20:29:00.23Z","modified":"2026-06-17T00:59:00.167Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"primary"},{"version":"2.0","score":6.6,"vector":"AV:L/AC:L/Au:N/C:N/I:C/A:C","level":"medium","assessor":"primary"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T14:04:08.01771Z"}],"osv":[{"id":"CVE-2017-1000255","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","status":"published","published":"2017-10-30T20:29:00Z","modified":"2026-04-10T03:54:36.750816Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:44:03.851821Z"},{"id":"DEBIAN-CVE-2017-1000255","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","status":"published","published":"2017-10-30T20:29:00.23Z","modified":"2026-09-01T20:03:40.400522748Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:45:28.207321Z"},{"id":"RHSA-2018:0654","title":"Red Hat Security Advisory: kernel-alt security, bug fix, and enhancement update","status":"published","published":"2024-09-16T00:48:58Z","modified":"2026-06-29T10:19:36Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"UBUNTU-CVE-2017-1000255","description":"On Linux running on PowerPC hardware (Power8 or later) a user process can craft a signal frame and then do a sigreturn so that the kernel will take an exception (interrupt), and use the r1 value *from the signal frame* as the kernel stack pointer. As part of the exception entry the content of the signal frame is written to the kernel stack, allowing an attacker to overwrite arbitrary locations with arbitrary values. The exception handling does produce an oops, and a panic if panic_on_oops=1, but only after kernel memory has been over written. This flaw was introduced in commit: \"5d176f751ee3 (powerpc: tm: Enable transactional memory (TM) lazily for userspace)\" which was merged upstream into v4.9-rc1. Please note that kernels built with CONFIG_PPC_TRANSACTIONAL_MEM=n are not vulnerable.","status":"published","published":"2017-10-09T00:00:00Z","modified":"2026-02-04T04:32:12.369799Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T15:54:13.729565Z"},{"id":"USN-3443-2","title":"linux-hwe vulnerabilities","description":"\nUSN-3443-1 fixed vulnerabilities in the Linux kernel for Ubuntu 17.04.\nThis update provides the corresponding updates for the Linux Hardware\nEnablement (HWE) kernel from Ubuntu 17.04 for Ubuntu 16.04 LTS.\n\nIt was discovered that on the PowerPC architecture, the kernel did not\nproperly sanitize the signal stack when handling sigreturn(). A local\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2017-1000255)\n\nAndrey Konovalov discovered that a divide-by-zero error existed in the TCP\nstack implementation in the Linux kernel. A local attacker could use this\nto cause a denial of service (system crash). (CVE-2017-14106)\n","status":"published","published":"2017-10-10T18:00:07Z","modified":"2026-02-10T04:41:13Z","updated_at":"2026-11-02T16:58:13.496563Z"}]}}