In the Linux kernel, the following vulnerability has been resolved:
virtio_net: Add hash_key_length check
Add hash_key_length check in virtnet_probe() to avoid possible out of
bound errors when setting/reading the hash key.
Security readout for executives and security teams
Plain-English summary
A Linux virtio_net driver flaw can cause memory access outside intended bounds when an invalid hash-key length is handled. Successful exploitation could threaten confidentiality, integrity, and availability, but the supplied evidence does not establish remote reachability, code execution, or exploitation in the wild.
Executive priority
Treat as a high-priority kernel maintenance issue on systems using virtio_net. Accelerate validation and patching where untrusted local workloads exist. Emergency incident response is not supported solely by this record because active exploitation is not established.
Technical view
virtnet_probe() lacked validation of hash_key_length before setting or reading the virtio network hash key, creating possible out-of-bounds access. The record classifies it as CWE-125 with CVSS 3.1 score 8.4 and a local, low-complexity, no-privilege, no-interaction vector. Kernel stable commits add the missing check.
Likely exposure
Exposure requires an affected Linux kernel and use of the virtio_net code path during device probing. The bundle lists versions spanning 5.18 through several fixed stable releases, but its version entries are insufficient to define every vulnerable distribution package precisely. Confirm status through the relevant Linux distributor.
Exploitation context
The CVSS vector describes a local attack path requiring neither privileges nor user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. Preconditions and practical impact beyond possible out-of-bounds errors are not documented in the bundle.
Researcher notes
The central issue is missing bounds validation for hash_key_length in virtnet_probe(). Multiple stable-tree commits indicate backports across kernel branches. The supplied affected-version data appears mixed and duplicated, so commit ancestry or distributor package mapping is necessary. Avoid inferring remote exploitation or arbitrary code execution from the CVSS impacts alone.
Mitigation direction
Install a distributor-supported kernel containing the applicable virtio_net stable fix.
Reboot into the updated kernel and retire vulnerable kernel packages where operationally appropriate.
Check Linux distributor guidance for exact package versions and required maintenance.
Prioritize systems using virtio_net when scheduling remediation.
Validation and detection
Inventory running kernel versions, not merely installed package versions.
Determine whether virtio_net is present and used on each potentially affected system.
Compare kernel packages against distributor advisories and the referenced stable fixes.
After updating, verify systems booted into the intended fixed kernel.
Review kernel logs for virtio_net faults or memory-access warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.