CVE-2025-69418

Publication date 27 January 2026

Last updated 28 January 2026

Ubuntu priority

Low

Why this priority?

Description

Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.

Read the notes from the security team

Why is this CVE low priority?

OpenSSL developers have rated this issue to be low severity

Learn more about Ubuntu priority

Status

Package Ubuntu Release Status
openssl 25.10 questing
Fixed 3.5.3-1ubuntu3
25.04 plucky Ignored end of life, was needed
24.04 LTS noble
Fixed 3.0.13-0ubuntu3.7
22.04 LTS jammy
Fixed 3.0.2-0ubuntu1.21
20.04 LTS focal
Fixed 1.1.1f-1ubuntu2.24+esm2
18.04 LTS bionic
Fixed 1.1.1-1ubuntu2.1~18.04.23+esm7
16.04 LTS xenial  
Not affected
14.04 LTS trusty
Not affected
openssl1.0 25.10 questing Not in release
25.04 plucky Not in release
24.04 LTS noble Not in release
22.04 LTS jammy Not in release
18.04 LTS bionic
Not affected
nodejs 25.10 questing
Not affected
25.04 plucky
Not affected
24.04 LTS noble
Not affected
22.04 LTS jammy
Vulnerable
20.04 LTS focal
Not affected
18.04 LTS bionic
Needs evaluation
16.04 LTS xenial
Needs evaluation
14.04 LTS trusty
Not affected
edk2 25.10 questing
Needs evaluation
25.04 plucky Ignored end of life, was needs-triage
24.04 LTS noble
Needs evaluation
22.04 LTS jammy
Needs evaluation
20.04 LTS focal
Needs evaluation
18.04 LTS bionic
Needs evaluation
16.04 LTS xenial
Needs evaluation

Get expanded security coverage with Ubuntu Pro

Reduce your average CVE exposure time from 98 days to 1 day with expanded CVE patching, ten-years security maintenance and optional support for the full stack of open-source applications. Free for personal use.

Get Ubuntu Pro 30-day free trial

Notes

mdeslaur

edk2 in jammy embeds OpenSSL 1.1.1j edk2 in noble embeds OpenSSL 3.0.9 edk2 in plucky embeds OpenSSL 3.4.0 edk2 in questing embeds OpenSSL 3.4.0 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable

References

Related Ubuntu Security Notices (USN)

    • USN-7980-1
    • OpenSSL vulnerabilities
    • 27 January 2026
    • USN-7980-2
    • OpenSSL vulnerabilities
    • 27 January 2026

Other references