Description
In the Linux kernel, the following vulnerability has been resolved:

ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet

parse_tag_3_packet() set encrypted_key_size from the Tag 3 packet body
without bounding it against ECRYPTFS_MAX_KEY_BYTES (64). When
encrypted_key_size > 64, decrypt_passphrase_encrypted_session_key()
sets decrypted_key_size = encrypted_key_size and performs two
out-of-bounds writes:

1. crypto_skcipher_decrypt() writes encrypted_key_size bytes into
decrypted_key[64] via scatterlist, overflowing into the parent
ecryptfs_auth_tok struct.
2. memcpy(crypt_stat->key, decrypted_key, decrypted_key_size) writes
into crypt_stat->key[64], corrupting root_iv, keysig_list, and
mutexes in ecryptfs_crypt_stat.

Only AES-192 (cipher code 0x08) enables this because it sets
crypt_stat->key_size = 24 independently of encrypted_key_size,
allowing crypto_skcipher_setkey() to succeed while encrypted_key_size
exceeds ECRYPTFS_MAX_KEY_BYTES.

The PKI decryption path (parse_tag_65_packet) already validates
decrypted_key_size <= ECRYPTFS_MAX_KEY_BYTES; the passphrase path
omits this check.

Bound encrypted_key_size against ECRYPTFS_MAX_KEY_BYTES (64) rather
than ECRYPTFS_MAX_ENCRYPTED_KEY_BYTES (512). The 64-byte limit also
protects the 512-byte encrypted_key[] buffer, so the former 512-byte
check is removed as redundant.

[tyhicks: Adjust the code comment to refer to macros representing the
buffer sizes rather than mentioning the buffer size values since they
may change in the future]
Published: 2026-09-11
Score: 6.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Remote Code Execution or local privilege escalation through kernel out‑of‑bounds writes
Action: Immediate Patch
AI Analysis

Impact

When parsing an ecryptfs Tag 3 packet, the kernel assigns an oversized encrypted_key_size (>64) to an internal buffer without validating the bound. With this field ignored, allowing crypto_skcipher_decrypt() to write more bytes than the buffer can hold and memcpy() to overflow into surrounding structures. This memory corruption can lead to arbitrary code execution, denial of service, or privilege escalation.

Affected Systems

All Linux kernel releases that implement ecryptfs and have not yet integrated the patch. The flaw is tied to AES‑192 usage, so systems configured to use this cipher are at risk. No specific version range is listed; any kernel containing the vulnerable parse_tag_3_packet implementation is potentially affected.

Risk and Exploitability

The EPSS score is less than 1% and the vulnerability is not listed in CISA KEV. Although the flaw involves a kernel heap buffer overflow, the CVSS score of 6.3 indicates moderate severity. An attacker with the ability to supply a malicious ecryptfs Tag 3 packet, or otherwise trigger the vulnerable code path, could drive the kernel into executing arbitrary code or causing a denial of service. A public exploit has not yet been disclosed, so the risk depends on the attacker’s ability to influence file operations on affected systems. Applying the corrective patch is strongly recommended.

Generated by OpenCVE AI on September 12, 2026 at 17:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to a Linux kernel release that contains the commit which bounds encrypted_key_size in parse_tag_3_packet.
  • Re‑mount the filesystem after upgrading the kernel to ensure that no corrupted key data remains in memory.
  • If the kernel upgrade cannot be applied immediately, temporarily disable the use of AES‑192 encryption for ecryptfs or avoid mounting ecryptfs volumes until the patch is installed.

Generated by OpenCVE AI on September 12, 2026 at 17:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 12 Sep 2026 17:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119

Sat, 12 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787
References
Metrics threat_severity

None

cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H'}

threat_severity

Moderate


Sat, 12 Sep 2026 08:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119

Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet parse_tag_3_packet() set encrypted_key_size from the Tag 3 packet body without bounding it against ECRYPTFS_MAX_KEY_BYTES (64). When encrypted_key_size > 64, decrypt_passphrase_encrypted_session_key() sets decrypted_key_size = encrypted_key_size and performs two out-of-bounds writes: 1. crypto_skcipher_decrypt() writes encrypted_key_size bytes into decrypted_key[64] via scatterlist, overflowing into the parent ecryptfs_auth_tok struct. 2. memcpy(crypt_stat->key, decrypted_key, decrypted_key_size) writes into crypt_stat->key[64], corrupting root_iv, keysig_list, and mutexes in ecryptfs_crypt_stat. Only AES-192 (cipher code 0x08) enables this because it sets crypt_stat->key_size = 24 independently of encrypted_key_size, allowing crypto_skcipher_setkey() to succeed while encrypted_key_size exceeds ECRYPTFS_MAX_KEY_BYTES. The PKI decryption path (parse_tag_65_packet) already validates decrypted_key_size <= ECRYPTFS_MAX_KEY_BYTES; the passphrase path omits this check. Bound encrypted_key_size against ECRYPTFS_MAX_KEY_BYTES (64) rather than ECRYPTFS_MAX_ENCRYPTED_KEY_BYTES (512). The 64-byte limit also protects the 512-byte encrypted_key[] buffer, so the former 512-byte check is removed as redundant. [tyhicks: Adjust the code comment to refer to macros representing the buffer sizes rather than mentioning the buffer size values since they may change in the future]
Title ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-11T19:45:09.583Z

Reserved: 2026-09-11T19:38:34.733Z

Link: CVE-2026-89607

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-11T20:19:45.723

Modified: 2026-09-11T20:19:45.723

Link: CVE-2026-89607

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-11T19:45:09Z

Links: CVE-2026-89607 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-12T17:30:16Z

Weaknesses