CVE-2023-31271 is a medium severity improper access control flaw, scored 6.7, in Intel Virtual RAID on CPU (VROC) software before version 8.0.8.1001. An authenticated local user could potentially escalate privileges. Update VROC to 8.0.8.1001 or later and check Intel advisory INTEL-SA-00953.
What's affected
The NVD record says improper access control (CWE-284) in some Intel VROC software before version 8.0.8.1001 may allow an authenticated user to potentially enable escalation of privilege through local access. The record is dated 2024-02-14 and the vector is CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H.
Note the vector: the attack needs high complexity and some user interaction, yet the impact figures are all high. That mix gives 6.7. The product matched in NVD is Intel Virtual RAID on CPU.
Intel's advisory page returned an access error to an automated request, so this post relies on the record for the fixed version. The record states 8.0.8.1001 as the first unaffected version. Read INTEL-SA-00953 itself for the full list of affected platforms and any operating system specific packages.
How to check if you're exposed
VROC is software that manages RAID volumes built on NVMe drives attached to the CPU. Check the installed version through the VROC management tooling on the host, or through your server vendor's system inventory, and compare it with 8.0.8.1001.
On Windows you can look in Apps and Features for the Intel VROC entry and read its version. On Linux the RAID stack is partly in the kernel and in mdadm, so follow the steps in the Intel advisory for what to check.
Servers from an OEM may carry the vendor's own driver package version. Use the OEM's notice to map it to Intel's fix.
What to do now
- List hosts that use Intel VROC and record the software version.
- Read INTEL-SA-00953 and the notice from your server vendor.
- Update to VROC 8.0.8.1001 or later, testing on one host before a wider rollout, since storage drivers touch boot and data paths.
- Take a verified backup before changing storage software.
- Limit who holds local or remote desktop logins on those hosts.
Why it matters
The class is CWE-284, which is a broad label for access checks that are missing or too loose. The advisory text does not publish the mechanism, so this post does not guess at it.
What the vector does tell you is the shape of the risk. An attacker needs a local account and a user to take some action, and the work is hard to get right. Those facts keep the score at medium. Still, storage software runs with high privilege, so shared machines, jump hosts and virtual desktops deserve earlier patching than a locked down single purpose server.
Quick check
What is the fixed version?
The record says the issue affects Intel VROC software before 8.0.8.1001. Update to 8.0.8.1001 or later and confirm in INTEL-SA-00953.
Does it need network access?
No. The vector is local (AV:L) and needs a low privilege account, so the risk is mostly on shared or multi-user hosts.
Sources
Last reviewed: 19 October 2026.