Without knowing the specific use case you have in mind, it sounds like both of these would fall under weaknesses related to time and state:
Weaknesses in this category are related to the improper management of time and state in an environment that supports simultaneous or near-simultaneous computation by multiple systems, processes, or threads.
Distributed computation is about time and state. That is, in order for more than one component to communicate, state must be shared, and all that takes time. Most programmers anthropomorphize their work. They think about one thread of control carrying out the entire program in the same way they would if they had to do the job themselves. Modern computers, however, switch between tasks very quickly, and in multi-core, multi-CPU, or distributed systems, two events may take place at exactly the same time. Defects rush to fill the gap between the programmer's model of how a program executes and what happens in reality. These defects are related to unexpected interactions between threads, processes, time, and information. These interactions happen through shared state: semaphores, variables, the file system, and, basically, anything that can store information."
As a side note, DARPA is interested in hardware specific vulnerabilities as well and has created a new program (SSITH) with the goal of addressing them:
In the announcement, they call out several categories of the CWE that are applicable to hardware:
"In cyberjargon, these classes are: permissions and privileges, buffer errors, resource management, information leakage, numeric errors, crypto errors, and code injection"
which seems like an odd set of selections, although they all could arguably be hardware-impacting at some level.
may make for some interesting reading on classifying hardware-related issues as well.