CVE-2026-89606
moderateInteger underflow in Linux kernel eCryptfs tag 70 packet parsing
The Linux kernel's eCryptfs stacked cryptographic filesystem contains an integer underflow in ecryptfs_parse_tag_70_packet(), which derives the encrypted filename size by subtracting fixed metadata fields from the parsed packet body size. A locally privileged attacker can trigger the flaw by supplying a malformed tag 70 packet (used for encrypted filenames) whose body is smaller than the fixed signature and cipher-code fields, causing the size calculation to wrap around. Successful exploitation can lead to kernel memory corruption (out-of-bounds access) with high impact on confidentiality, integrity, and availability, most plausibly a local privilege escalation or kernel crash. Only systems actually using eCryptfs filesystems (such as legacy Ubuntu encrypted-home setups) with untrusted local users are exposed; the flaw is not remotely triggerable and there is no evidence of exploitation in the wild.
What to do: Apply kernel updates containing the upstream eCryptfs fix once your distribution ships it; no fixed version numbers were specified in the source data. If eCryptfs is not needed, blacklist the ecryptfs module to eliminate the attack surface entirely. Audit for exposure by checking for eCryptfs mounts (mount | grep ecryptfs) or ~/.ecryptfs / /home/.ecryptfs directories, and restrict untrusted local accounts on hosts where eCryptfs remains in use.
| Linux kernel (eCryptfs subsystem) | — |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
- Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
In the news0 stories
No ingested article mentions this CVE yet.