CVE-2017-1000255
Last modified
CVE-2017-1000255 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.38% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | All versions |
References
- http://www.securityfocus.com/bid/101264Third Party Advisory, VDB Entry
- https://access.redhat.com/security/cve/CVE-2017-1000255Issue Tracking, Third Party Advisory
- http://www.securityfocus.com/bid/101264Third Party Advisory, VDB Entry
- https://access.redhat.com/security/cve/CVE-2017-1000255Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-1000255?
How severe is CVE-2017-1000255?
How do I fix CVE-2017-1000255?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-1000249An issue in file() was introduced in commit 9611f31313a93aa0…
- CVE-2017-1000250All versions of the SDP server in BlueZ 5.46 and earlier are…
- CVE-2017-1000251The native Bluetooth stack in the Linux Kernel (BlueZ), star…8
- CVE-2017-1000252The KVM subsystem in the Linux kernel through 4.13.3 allows …
- CVE-2017-1000253Linux distributions that have not patched their long-term ke…7.8
- CVE-2017-1000254libcurl may read outside of a heap allocated buffer when doi…
- CVE-2017-1000256libvirt version 2.3.0 and later is vulnerable to a bad defau…8.1
- CVE-2017-1000257An IMAP FETCH response line indicates the size of the return…9.1
- CVE-2017-10003Vulnerability in the Solaris component of Oracle Sun Systems…
- CVE-2017-1000353Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and …9.8
- CVE-2017-1000354Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and …
- CVE-2017-1000355Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and …
Are you affected by CVE-2017-1000255?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
