CVE-2026-23432: mshv: Fix use-after-free in mshv_map_user_memory error path
In the Linux kernel, the following vulnerability has been resolved:
mshv: Fix use-after-free in mshv_map_user_memory error path
In the error path of mshv_map_user_memory(), calling vfree() directly on
the region leaves the MMU notifier registered. When userspace later unmaps
the memory, the notifier fires and accesses the freed region, causing a
use-after-free and potential kernel panic.
Replace vfree() with mshv_partition_put() to properly unregister
the MMU notifier before freeing the region.
Security readout for executives and security teams
Plain-English summary
A Linux kernel memory-cleanup error can leave a callback pointing to freed memory. A later memory unmap may trigger the stale callback, causing a kernel crash and potentially broader security impact. Exploitation requires local, low-privileged access; the supplied sources do not establish remote or active exploitation.
Executive priority
Treat as a high-priority local kernel issue, especially on shared or tenant-facing systems. Schedule prompt vendor-supported kernel updates after confirming exposure. Emergency internet-edge action is not supported by the evidence because the vector is local and active exploitation is not documented.
Technical view
The error path in mshv_map_user_memory() directly calls vfree() without unregistering its MMU notifier. A later userspace unmap can invoke that notifier against the freed region, producing a use-after-free and possible kernel panic. The fix uses mshv_partition_put() so notifier removal occurs before the region is freed.
Likely exposure
Exposure is most likely on systems running affected Linux kernel builds where the mshv functionality is available to a local user. The supplied affected-version encoding references 6.19, 6.19.10, and 7.0 but does not clearly establish all boundaries. Distribution backports require separate confirmation.
Exploitation context
CVSS 3.1 scores this 7.8 with local access, low complexity, low privileges, and no user interaction. The bundle marks KEV false and provides no evidence of exploitation in the wild or a public exploit.
Researcher notes
The documented failure is an error-path lifetime-management flaw involving a registered MMU notifier. The supplied description explicitly supports use-after-free and potential panic; confidentiality and integrity impact appear in the CVSS vector but are not independently demonstrated. Exact affected-version boundaries and exploitability beyond denial of service remain incomplete.
Mitigation direction
Apply a vendor-supported kernel release containing the applicable referenced fix or backport.
Prioritize multi-user, tenant-facing, and other systems where untrusted local users can access affected functionality.
Consult the Linux or distribution vendor when kernel fix provenance cannot be confirmed.
Validation and detection
Inventory kernel versions and compare them with vendor advisories and backport records.
Confirm the running kernel includes an applicable referenced fix or equivalent mshv_partition_put() change.
Determine whether affected mshv functionality is present and accessible to untrusted local users.
Review kernel crash records for use-after-free or MMU-notifier failures involving mshv.
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.
cve · low confidence lookup
CVE-2026-23432 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
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.