CVE-2026-64532

CVE CVE-2026-64532EUVD EUVD-2026-49110Published 2026-07-27T06:32:33.000ZLast changed 2026-08-05T12:42:42.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound NTFS_DE view.data_off in UpdateRecordData{Root,Allocation} In do_action()'s UpdateRecordDataRoot (fslog.c:3489) and UpdateRecordDataAllocation (fslog.c:3697) cases, the memmove destination is `Add2Ptr(e, le16_to_cpu(e->view.data_off))`, where e->view.data_off comes from an on-disk NTFS_DE inside an INDEX_ROOT or INDEX_BUFFER. Neither case validates view.data_off + dlen against e->size; the existing check_if_index_root / check_if_alloc_index helpers walk the entry chain and validate the entry's offset, but not its internal view fields. The neighbouring read sites (e.g., fs/ntfs3/index.c when iterating view entries) check view.data_off + view.data_size <= e->size. Apply the same bound at the two memmove sites. Reproduced under UML+KASAN on mainline 8d90b09e6741 via pr_warn-only probe instrumentation: with view.data_off forced to 0xFFFC, the memmove writes 32 bytes past the end of the NTFS_DE. This is similar in shape to Pavitra Jha's 2026-05-02 patch "fs/ntfs3: prevent oob in case UpdateRecordDataRoot" (<20260502105008.21827-1-jhapavitra98@gmail.com>) which proposes calling ntfs3_bad_de_range(); that helper does not exist in mainline. This patch uses inline checks.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux b46acd6a6a627d876898e1c84d3f84902264b445 <be306b8d9143a9c076c804a7ca025d69caf9c448; b46acd6a6a627d876898e1c84d3f84902264b445 <3e127829e57f5190f612412ece4541cb96d5ec7a; patch: 6.12.97; 5.15; patch: 6.18.40; patch: 5.15.212; b46acd6a6a627d876898e1c84d3f84902264b445 <315d3a9a48b49f889da3d858a9307e677cb9e1bd; b46acd6a6a627d876898e1c84d3f84902264b445 <d41b382068ca4e64e421f736cdd700095464b6ac; b46acd6a6a627d876898e1c84d3f84902264b445 <b20e5a709d8bd190d6e4645606763c7423e694c1; patch: 7.2-rc1; b46acd6a6a627d876898e1c84d3f84902264b445 <429d653ca641d38a78609b8f62e81a0a5c780a2d; patch: 7.1.5; patch: 6.6.145; patch: 6.1.178; patch: 0; b46acd6a6a627d876898e1c84d3f84902264b445 <36feda687afebae24c472202694448738809c411

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.