Advisory

UBUNTU-CVE-2025-69418

Also known as: CVE-2025-69418

Summary

The record has no summary.

Details

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.

Severity

Medium Basis: CVSS v3 score 4, vector CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Dates

Published
2026-01-27 00:00 UTC
Modified
2026-10-17 12:58 UTC

Affected packages and fixes

11 affected packages
PackageSystemAffectedFix
edk2Debian packages (deb) · Ubuntu 22.04introduced 0No fixed version is listed.
opensslDebian packages (deb) · Ubuntu 22.04Earlier versionssudo apt-get update && sudo apt-get upgrade
edk2Debian packages (deb) · Ubuntu 24.04introduced 0No fixed version is listed.
opensslDebian packages (deb) · Ubuntu 24.04Earlier versionssudo apt-get update && sudo apt-get upgrade
edk2Debian packages (deb) · Ubuntu 25.10introduced 0No fixed version is listed.
opensslDebian packages (deb) · Ubuntu 25.10Earlier versionssudo apt-get update && sudo apt-get upgrade
edk2Debian packages (deb) · Ubuntu 26.10introduced 0No fixed version is listed.
edk2-hweDebian packages (deb) · Ubuntu 26.10introduced 0No fixed version is listed.
edk2Debian packages (deb) · Ubuntu 26.04introduced 0No fixed version is listed.
edk2-hweDebian packages (deb) · Ubuntu 26.04introduced 0No fixed version is listed.
opensslDebian packages (deb) · Ubuntu 26.04Earlier versionssudo apt-get update && sudo apt-get upgrade

Some commands upgrade the distribution's packages. Compare the fixed version with the version you have installed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Ubuntu Security Notices · CC BY-SA 4.0

Sources & licences