In the Linux kernel, the following vulnerability has been resolved:
crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly
The existing allocation of scatterlists in omap_crypto_copy_sg_lists()
was allocating an array of scatterlist pointers, not scatterlist objects,
resulting in a 4x too small allocation.
Use sizeof(*new_sg) to get the correct object size.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory allocation bug in the OMAP crypto driver. A local, low-privileged user could potentially corrupt memory and affect confidentiality, integrity, and availability. It is high severity, but the source bundle does not show active exploitation or remote attack exposure.
Executive priority
Prioritize patch validation for embedded, industrial, and multi-user Linux systems that may include OMAP crypto support. Treat as high severity where the driver is present; otherwise confirm non-exposure rather than assuming fleet-wide impact.
Technical view
omap_crypto_copy_sg_lists() allocated an array sized for scatterlist pointers instead of scatterlist objects, making the allocation too small. The Linux fix changes allocation sizing to sizeof(*new_sg). CVSS 3.1 is 7.8 with local access, low complexity, low privileges, no user interaction, and high CIA impact.
Likely exposure
Exposure is most likely on Linux systems with affected kernels where the OMAP crypto driver is present and reachable. General-purpose servers without this driver or hardware path may not be exposed. Downstream vendor kernels need separate confirmation against the referenced stable commits or advisories.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The attack vector is local with low privileges, so risk is higher on multi-user systems, embedded devices, or appliances where untrusted users or workloads can reach kernel crypto paths.
Researcher notes
The evidence supports a kernel heap under-allocation in OMAP crypto scatterlist handling. The bundle provides fix commits and CVSS, but not a public proof of concept, exploitation evidence, or detailed product matrix beyond Linux and Siemens advisory references.
Mitigation direction
Update affected Linux kernels to versions containing the referenced stable fixes.
Check distribution or device vendor advisories for backported fixes.
Review Siemens SSA-253495 if Siemens products are in scope.
Restrict local shell or workload access on exposed embedded systems.
Disable unused OMAP crypto driver paths where vendor guidance supports it.
Validation and detection
Inventory kernel versions and downstream vendor patch levels.
Confirm whether the OMAP crypto driver is built, loaded, or reachable.
Compare deployed kernels against the referenced stable commit fixes.
Check vendor advisories for product-specific affected status.
Document compensating controls where immediate patching is not possible.
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-23222 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
1ADP providers
10Source 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.