LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53259: VMCI: check context->notify_page after call to get_user_pages_fast() to avoid GPF

In the Linux kernel, the following vulnerability has been resolved: VMCI: check context->notify_page after call to get_user_pages_fast() to avoid GPF The call to get_user_pages_fast() in vmci_host_setup_notify() can return NULL context->notify_page causing a GPF. To avoid GPF check if context->notify_page == NULL and return error if so. general protection fault, probably for non-canonical address 0xe0009d1000000060: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0x0005088000000300- 0x0005088000000307] CPU: 2 PID: 26180 Comm: repro_34802241 Not tainted 6.1.0-rc4 #1 Hardware name: Red Hat KVM, BIOS 1.15.0-2.module+el8.6.0 04/01/2014 RIP: 0010:vmci_ctx_check_signal_notify+0x91/0xe0 Call Trace: <TASK> vmci_host_unlocked_ioctl+0x362/0x1f40 __x64_sys_ioctl+0x1a1/0x230 do_syscall_64+0x3a/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel VMCI flaw where an unexpected NULL page after a memory-pinning call can crash kernel code. The public record shows a kernel fix, but gives no CVSS score and no confirmed active exploitation. Business urgency depends on whether affected kernels expose VMCI functionality.

Executive priority

Treat as a targeted kernel availability risk until asset exposure is known. Prioritize inventory and patching for systems with affected kernels and VMCI enabled, but do not assume active exploitation from the available evidence.

Technical view

In vmci_host_setup_notify(), get_user_pages_fast() can leave context->notify_page NULL. Later VMCI ioctl handling can dereference that state in vmci_ctx_check_signal_notify(), causing a general protection fault. The fix adds a NULL check and returns an error instead of continuing.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with VMCI code reachable. The bundle lists Linux kernel affected ranges and multiple stable fix commits, but does not identify distributions beyond a Debian LTS advisory reference.

Exploitation context

The source shows a crash from a repro process through the ioctl syscall path. KEV is false, and the bundle provides no evidence of active exploitation, public weaponization, privilege escalation, or remote reachability.

Researcher notes

Focus validation on VMCI ioctl reachability and kernel lineage. The evidence supports a NULL-check hardening fix for a GPF condition, but does not establish CVSS impact, attacker prerequisites, or exploitability beyond the reported crash path.

Mitigation direction

  • Apply kernel updates containing the referenced stable VMCI fix commits.
  • Follow distribution guidance, including the referenced Debian LTS advisory where applicable.
  • Prioritize kernels listed as affected in the CVE source bundle.
  • If no vendor package is available, track vendor kernel guidance before deploying changes.

Validation and detection

  • Inventory Linux kernel versions across systems.
  • Confirm whether VMCI functionality is enabled or reachable on affected hosts.
  • Check installed kernel changelogs for the referenced stable commit IDs.
  • Review Debian LTS or distribution advisories for package-specific fixed versions.
Prepared
Confidence
medium
Sources
9

Public sources used

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-2023-53259 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
1ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa1d88436d53a75e950db15834b3d2f8c0c358fdc, a1d88436d53a75e950db15834b3d2f8c0c358fdc, a1d88436d53a75e950db15834b3d2f8c0c358fdc, a1d88436d53a75e950db15834b3d2f8c0c358fdc, a1d88436d53a75e950db15834b3d2f8c0c358fdc, a1d88436d53a75e950db15834b3d2f8c0c358fdcunaffected
LinuxLinux4.0, 0, 5.4.296, 5.10.240, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.