KernelScan.io

HIGH Introduced in 2.6.29

ecryptfs Tag70Packet Underflow

CVE-2026-89606

CVSS 7.8 / 10.0 NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

KernelScan AI7.8HIGH

01

In the Linux kernel, the following vulnerability has been resolved: ecryptfs: reject too-small tag 70 packets ecryptfs_parse_tag_70_packet() subtracts fixed metadata fields from the parsed packet body size to derive the encrypted filename size. A malformed packet with a body smaller than those fixed fields can underflow that size calculation. Reject tag 70 packets before the subtraction unless the body contains the signature, cipher code, and at least one byte of encrypted filename data.

02

Engine v0.6.0

Risk summary

A malformed encrypted filename in eCryptfs's lower filesystem can cause an integer underflow in the tag 70 packet parser, leading to memory corruption. Any user who can access files on a mounted eCryptfs filesystem can trigger the bug, though planting the malformed data requires control of the lower filesystem (via removable media, a malicious network share, or direct write access). Systems using eCryptfs with untrusted lower filesystems are at highest risk.

Affectedfs/ecryptfs/keystore.c (ecryptfs)

Vulnerability analysis

When eCryptfs parses a tag 70 packet (an encrypted filename), it subtracts fixed metadata field sizes from the packet body size to determine the encrypted filename length. A malformed packet whose body is smaller than those fixed fields causes this subtraction to underflow, producing an extremely large size value that is then used for memory allocation and data copying — potentially corrupting kernel heap memory. The fix adds a validation check that rejects any tag 70 packet whose body is too small to contain the signature, cipher code, and at least one byte of filename data, before the subtraction is performed. The bug can be triggered by any user who accesses a file on an already-mounted eCryptfs filesystem, but the malformed filename must first be planted in the lower filesystem — achievable through removable media, a malicious or MITM'd network filesystem server, or direct write access by a privileged user.

03

BranchIntroducedFixed inPatch commit
5.102.6.295.10.270df5f375a6151
5.152.6.295.15.2215668121974eb
6.12.6.296.1.1882e5afed9503d
6.122.6.296.12.1099d88391bbed7
6.182.6.296.18.50b31da1ecf139
6.62.6.296.6.157414a0f04feb0
7.22.6.297.2.4d2869768eab5
mainline2.6.297.3e97bbe1b2bd8
cip/5.102.6.295.10.271-cip78df5f375a6151
cip/6.12.6.296.1.189-cip612e5afed9503d
cip/6.1-rt2.6.296.1.189-cip61-rt322e5afed9503d
cip/6.122.6.296.12.111-cip329d88391bbed7

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.111-cip32
cip/6.1Fixed in 6.1.189-cip61
cip/6.1-rtFixed in 6.1.189-cip61-rt32
cip/5.10Fixed in 5.10.271-cip78
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.268-cip77-rt34)
cip/4.19Affected — no CIP fix yet (latest 4.19.325-cip136)
cip/4.19-rtAffected — no CIP fix yet (latest 4.19.325-cip136-rt50)
cip/4.4Affected — no CIP fix yet (latest 4.4.302-cip115)
cip/4.4-rtAffected — no CIP fix yet (latest 4.4.302-cip115-rt63)