CVE-2026-23222: crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly

Published Feb 18, 2026
·
Updated

crypto: omap - Allocate OMAPCRYPTOFORCECOPY scatterlists correctly

Affected Software

11 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.121.1-1
Microsoft cbl2 kernel 5.15.200.1-1
Linux Linux kernel>=4.13<5.10.251
Linux Linux kernel>=5.11<5.15.201
Linux Linux kernel>=5.16<6.1.164
Linux Linux kernel>=6.2<6.6.125
Linux Linux kernel>=6.7<6.12.72
Linux Linux kernel>=6.13<6.18.11
Linux Linux kernel>=6.19<6.19.1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1

Event History

Feb 18, 2026
CVE Published
via MITRE·02:53 PM
Data Sourced
via MITRE·02:53 PM
DescriptionSeverity
Data Sourced
via NVD·04:22 PM
RemedyDescriptionSeverityAffected Software
Feb 21, 2026
Data Sourced
via Microsoft·12:28 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-23222?

CVE-2026-23222 has been rated as having a high severity due to potential impact on system performance and security.

2

How do I fix CVE-2026-23222?

To fix CVE-2026-23222, update your Linux kernel to the latest stable release where the vulnerability has been patched.

3

What is the affected software for CVE-2026-23222?

CVE-2026-23222 affects the Linux kernel, specifically related to the crypto module for OMAP devices.

4

What can happen if CVE-2026-23222 is exploited?

If exploited, CVE-2026-23222 can lead to memory corruption and potential denial of service in affected systems.

5

Is there a workaround for CVE-2026-23222?

There is no standardized workaround for CVE-2026-23222; updating the kernel is the recommended course of action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203