Skip to main content

Linux Kernel EUVDEUVD-2026-49111

| CVE-2026-64533 HIGH
2026-07-27 Linux GHSA-hvv2-rwwx-6q3h
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI
7.8 HIGH

Local delivery of a crafted image (AV:L) that a user/automount must mount (UI:R); no attacker privileges needed (PR:N); kernel-memory overflow yields high C/I/A.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 30, 2026 - 06:44 vuln.today
CVSS changed
Jul 30, 2026 - 06:37 NVD
7.8 (HIGH)
Patch available
Jul 27, 2026 - 09:01 EUVD
CVE Published
Jul 27, 2026 - 06:32 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 27, 2026 - 06:32 cve.org
HIGH 7.8

DescriptionCVE.org

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

fs/ntfs3: validate lcns_follow in log_replay conversion

log_replay() converts DIR_PAGE_ENTRY_32 records into DIR_PAGE_ENTRY records when replaying version 0 restart tables.

During this conversion, the memmove() length is derived directly from the on-disk lcns_follow field:

memmove(&dp->vcn, &dp0->vcn_low, 2 * sizeof(u64) + le32_to_cpu(dp->lcns_follow) * sizeof(u64));

check_rstbl() validates restart table structure, but does not constrain per-entry lcns_follow values relative to the entry size. A malformed filesystem image can provide an oversized lcns_follow value, causing the conversion memmove() to access memory beyond the bounds of the allocated restart table buffer.

The same field is later used to bound iteration over page_lcns[], so validating lcns_follow during conversion also prevents downstream out-of-bounds access from the same malformed metadata.

Compute the maximum valid lcns_follow from the already-validated restart table entry size and reject entries that exceed this bound. Reuse the existing t16/t32 scratch variables already declared in log_replay() to avoid introducing new declarations.

[almaz.alexandrovich@paragon-software.com: fixed the conflicts]

AnalysisAI

Out-of-bounds memory access in the Linux kernel's ntfs3 filesystem driver allows a crafted NTFS image to corrupt kernel memory during NTFS log replay. When log_replay() converts version 0 restart-table records (DIR_PAGE_ENTRY_32 to DIR_PAGE_ENTRY), it derives a memmove() length directly from the attacker-controlled on-disk lcns_follow field, which check_rstbl() does not bound against the entry size; an oversized value drives reads/writes past the allocated restart-table buffer. There is no public exploit identified at time of analysis and EPSS is low (0.17%), but the flaw carries CVSS 7.8 with high confidentiality, integrity, and availability impact because it executes in kernel context when a malicious volume is mounted.

Technical ContextAI

The affected component is the ntfs3 in-kernel driver, Paragon's read/write NTFS implementation merged into mainline Linux. The bug lives in the journal/log recovery path (log_replay()) that processes NTFS $LogFile restart tables. During conversion of legacy 32-bit directory-page entries to the current DIR_PAGE_ENTRY layout, the code copies vcn and page_lcns[] data using a length computed as 2*sizeof(u64) + lcns_follow*sizeof(u64). The lcns_follow field is read straight from on-disk metadata; check_rstbl() validates overall restart-table structure but never constrains per-entry lcns_follow relative to the validated entry size, so an inflated count makes memmove() run off the end of the buffer. The same unvalidated field later bounds iteration over page_lcns[], creating a second downstream out-of-bounds read from the same metadata. Although the CWE is listed as N/A, this is a classic buffer overflow / improper bounds validation (CWE-787/CWE-125 class), and the fix computes a maximum valid lcns_follow from the already-validated entry size and rejects entries exceeding it.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, or 7.2-rc1 (or later within each series), which add validation of lcns_follow against the restart-table entry size. Apply the fix from your distribution's kernel updates or the mainline stable commits at https://git.kernel.org/stable/c/159f694d682e4215b3822ae31ed3a4631628fe55 and related hashes. Where patching must be deferred, the most effective compensating control is to prevent mounting of untrusted NTFS volumes: disable or restrict automount of removable media (e.g. udisks/autofs policies), and where ntfs3 is not needed, blacklist the module (add 'blacklist ntfs3' to modprobe config) so crafted images cannot reach the vulnerable code - the trade-off is loss of native NTFS read/write support. For systems that must handle untrusted NTFS images, process them in an isolated VM or unprivileged container rather than mounting on the host. Restricting mount privileges to trusted administrators further limits exposure.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-49111 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy