CVE-2026-89607: ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 14cb36a500a5a3afbc955dbf69dabc565f1a3b26, 2cd21340163494d312836c77c9fbfe2530b3d075, 33e050cac841498b5175f0f385eee903fd98863c.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 14cb36a500a5a3afbc955dbf69dabc565f1a3b26, 2cd21340163494d312836c77c9fbfe2530b3d075, 33e050cac841498b5175f0f385eee903fd98863c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.19affected
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before 2cd21340163494d312836c77c9fbfe2530b3d075affected · git
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before e2152d491ae62d96a32ed59778680a242af1fbc6affected · git
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before d2802414081184f79a619ede178aeef3aa989793affected · git
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before 33e050cac841498b5175f0f385eee903fd98863caffected · git
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before ccd13eff0e7356d2aa28b127b577e4e5ad4563f5affected · git
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before 14cb36a500a5a3afbc955dbf69dabc565f1a3b26affected · git
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before a419c9ebfc9a40ee56aaad6dc68bfd67d400817baffected · git
- 237fead619984cc48818fe12ee0ceada3f55b012 and later · before 5babe9c177c364521e3e682b949c5a8c47f4a441affected · git
- before 2.6.19not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89605Sep 11, 2026 · ecryptfs: release message context on send failure31Monitor
- ← EarlierCVE-2026-89606Sep 11, 2026 · ecryptfs: reject too-small tag 70 packets31Monitor
- Later →CVE-2026-89608Sep 11, 2026 · ecryptfs: pass packet set buffer size to parser28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 14cb36a500a5a3afbc955dbf69dabc565f1a3b26 | Vendor (CNA) |
| Linux Linux | 2cd21340163494d312836c77c9fbfe2530b3d075 | Vendor (CNA) |
| Linux Linux | 33e050cac841498b5175f0f385eee903fd98863c | Vendor (CNA) |
| Linux Linux | 5babe9c177c364521e3e682b949c5a8c47f4a441 | Vendor (CNA) |
| Linux Linux | a419c9ebfc9a40ee56aaad6dc68bfd67d400817b | Vendor (CNA) |
| Linux Linux | ccd13eff0e7356d2aa28b127b577e4e5ad4563f5 | Vendor (CNA) |
| Linux Linux | d2802414081184f79a619ede178aeef3aa989793 | Vendor (CNA) |
| Linux Linux | e2152d491ae62d96a32ed59778680a242af1fbc6 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2cd21340163494d312836c77c9fbfe2530b3d075
- git.kernel.org/stable/c/33e050cac841498b5175f0f385eee903fd98863c
- git.kernel.org/stable/c/5babe9c177c364521e3e682b949c5a8c47f4a441
- git.kernel.org/stable/c/a419c9ebfc9a40ee56aaad6dc68bfd67d400817b
- git.kernel.org/stable/c/ccd13eff0e7356d2aa28b127b577e4e5ad4563f5
- git.kernel.org/stable/c/d2802414081184f79a619ede178aeef3aa989793
- git.kernel.org/stable/c/e2152d491ae62d96a32ed59778680a242af1fbc6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.