Security readout for executives and security teams
Plain-English summary
CVE-2025-22018 is a Linux kernel crash vulnerability in ATM MPOA handling. A local user with access to the relevant socket path could trigger a NULL pointer dereference and crash the kernel, causing denial of service. The sources do not show data theft, privilege escalation, or confirmed active exploitation.
Executive priority
Treat as a routine but real availability risk. Prioritize multi-user Linux systems, shared hosting, and operationally critical hosts where a local crash could interrupt services. It is below urgent exploited-in-the-wild issues unless your environment depends on affected ATM/MPOA paths.
Technical view
The flaw is a CWE-476 NULL pointer dereference in MPOA_cache_impos_rcvd(). When both entry and holding_time are NULL, entry can still be passed to eg_cache_put(), where entry->use is referenced. The published CVSS is 5.5, local attack vector, low privileges required, and availability impact high.
Likely exposure
Exposure is most relevant to Linux systems running affected kernels with ATM/MPOA functionality reachable by local users. The bundle identifies Linux kernel versions and stable kernel fixes, but does not provide CPEs or distribution-wide affected package mapping beyond Debian LTS announcements.
Exploitation context
The evidence supports local, low-privilege denial of service. KEV is false, and the provided sources do not report active exploitation. The included KASAN trace shows a reproducible kernel crash path, but no source demonstrates remote exploitation or code execution.
Researcher notes
The core condition is the missing guard for simultaneous NULL entry and holding_time before cache removal logic dereferences entry. The bundle gives stable commit references and Debian LTS notices, but not full per-distribution status or proof of exploitation beyond the crash evidence.
Mitigation direction
Upgrade to a vendor kernel containing the referenced stable fixes.
Apply relevant Debian LTS kernel updates where applicable.
Check vendor advisories for exact fixed package versions.
Limit local access to systems where ATM/MPOA is enabled or required.
Retire unused ATM/MPOA functionality if supported by your platform policy.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Confirm whether ATM/MPOA kernel functionality is present or enabled.
Map installed packages against vendor advisories and stable kernel fixes.
Review kernel crash logs for MPOA, eg_cache, or vcc_sendmsg traces.
Track remediation through normal kernel reboot verification.
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-476: 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-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.