CVE-2026-0106

In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check

Critical · published February 5, 2026

CVSS v3.1
9.3
EPSS
0%
Percentile
1.7
In the wild
Unconfirmed
What it is

🔥 A missing bounds check in vpu_mmap could let attackers **map any address** without breaking a sweat! Think of it like a hotel without a security desk, where anyone can enter and access any room, regardless of their booking — once inside, they can do whatever they please! This vulnerability opens the door for local escalation of privilege, meaning an attacker could gain unauthorized access to sensitive areas of the system and execute their malicious plans freely. The stakes are high with no need for additional permissions or user interaction, making it particularly dangerous.

Put simply

Think of it like a hotel without a security desk, where anyone can enter and access any room, regardless of their booking — once inside, they can do whatever they please! The flaw in vpu_ioctl allows arbitrary address mapping due to the absence of a bounds check, which can lead to privilege escalation for local users without needing elevated execution rights.

What to do

This vulnerability opens the door for local escalation of privilege, meaning an attacker could gain unauthorized access to sensitive areas of the system and execute their malicious plans freely. The stakes are high with no need for additional permissions or user interaction, making it particularly dangerous. Immediate action is crucial! Apply the latest patches as soon as they're available to close this gap. Review your security policies and ensure that only trusted users have access to critical system resources. Take this seriously! You've got this! Patch up and secure your systems, and you'll be a security hero! 🛡️

The record
Technical detail
CVSS v3.1
9.3 · CRITICAL
Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00119 · 1.7th percentile
Published
2026-02-05T20:19Z
EPSS history
Timeline
  • 05 FEB 20:19Z
    In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check
    cvelistv5