Home/CVE/The start_thread function in arch/powerpc/kernel/process.c in the Linux kernel through 4.6.3 on powerpc platforms mishan
CVE

CVE-2016-5828

The start_thread function in arch/powerpc/kernel/process.c in the Linux kernel through 4.6.3 on powerpc platforms mishan

The start_thread function in arch/powerpc/kernel/process.c in the Linux kernel through 4.6.3 on powerpc platforms mishandles transactional state, which allows local users to cause a denial of service (invalid process state or TM Bad Thing exception, and system crash) or possibly have unspecified other impact by starting and suspending a transaction before an exec system call.

HIGH · CVSS 7.8 EPSS 0.00446
EPSS exploitation odds0.45% · top 63%
Schedule remediation
  • CVSS base score ≥ 7.0
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2016-5828, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

Severity & exploitation scoring

View on NVD →
CVSS base score
7.8
HIGHCVSS v3.1 · [email protected]
EPSS exploitation probability
0.45%
Top 63%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle
  1. 27 Jun 2016Published to NVD
  2. 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small marks a technique that N independent sources agree on.

▤ Build a SIEM detection for these techniques

Weakness Classification

Affected Products & Versions

10
linux kernel>= 3.9 and < 3.10.103
linux kernel>= 3.11 and < 3.14.74
linux kernel>= 3.15 and < 3.16.37
linux kernel>= 3.17 and < 3.18.37
linux kernel>= 3.19 and < 4.1.28
linux kernel>= 4.2 and < 4.4.16
linux kernel>= 4.6 and < 4.6.5
debian linuxall versions
📦

Fixed versions by distribution

22
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle allkernel open
oracle allkernel-abi-whitelists open
oracle allkernel-debug open
oracle allkernel-debug-devel open
oracle allkernel-devel fixed in 0:3.10.0-514.el7
oracle allkernel-headers fixed in 0:3.10.0-514.el7
oracle allkernel-tools open
oracle allkernel-tools-libs fixed in 0:3.10.0-514.el7
oracle allkernel-tools-libs-devel fixed in 0:3.10.0-514.el7
oracle allperf fixed in 0:3.10.0-514.el7
oracle allpython-perf open
suse sle15kernel-default open
suse sle15kernel-default-base open
suse sle15kernel-default-devel open
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-devel-rt open
suse sle15kernel-macros open
suse sle15kernel-source open
suse sle15kernel-source-azure open
suse sle15kernel-source-rt open
suse sle15reiserfs-kmp-default open

Vendor Advisories

11
rhsaRHSA-2016:2574Moderate
suse-csafrhsa-2016_2574
🔗

References & Sources

14
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.