CVE-2026-72195
CVE CVE-2026-72195EUVD EUVD-2026-58953Published 2026-08-15T05:53:54.000ZLast changed 2026-08-17T05:41:21.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound attr_off in UpdateResidentValue against data_off In do_action()'s UpdateResidentValue case (fslog.c:3307), lrh->attr_off and lrh->redo_len come from the on-disk LRH. When they satisfy aoff + dlen < attr->res.data_off, the assignment attr->res.data_size = cpu_to_le32(aoff + dlen - data_off); underflows to ~4 GiB (e.g. 0xFFFFFFF9 when aoff=0x10, dlen=1, data_off=0x18). Subsequent code that reads attr->res.data_size to walk the resident attribute payload would then read up to 4 GiB past the 1024-byte MFT record allocation. The existing mi_enum_attr() defense in fs/ntfs3/record.c:287 catches the corrupted data_size on the next attribute walk and fails the mount, but only on the path that walks all attributes. A read site that picks an attribute by name and reads its data_size without re-validating is not covered. Validate aoff against data_off and asize at the source. Reproduced under UML+KASAN on mainline 8d90b09e6741 via pr_warn-only probe: with aoff=0x10 and data_off=0x18, the post-assignment data_size is 0xfffffff9 (mount then fails at -22 from mi_enum_attr). [almaz.alexandrovich@paragon-software.com: clang-formatted the changes]
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 patch: 7.1.5; b46acd6a6a627d876898e1c84d3f84902264b445 <a89c66674283a0293c0f266dc57087a6114371a3; b46acd6a6a627d876898e1c84d3f84902264b445 <d1570c48f49a693974d000251030370ee2e83539; b46acd6a6a627d876898e1c84d3f84902264b445 <50b5e83384e7fed3d11d18b79ff350e9d6d89861; patch: 7.2; patch: 5.15.212; b46acd6a6a627d876898e1c84d3f84902264b445 <ab8761676d638c5be170aaf91b7ffdd451236616; b46acd6a6a627d876898e1c84d3f84902264b445 <546518468e6c9ea469669eef78f8cc380ad6e2ca; patch: 0; patch: 6.1.178; 5.15; patch: 6.12.97; b46acd6a6a627d876898e1c84d3f84902264b445 <53c12f178f584dc5f836ffe2782138a6e9348ed9; patch: 6.18.40; b46acd6a6a627d876898e1c84d3f84902264b445 <97758fd9756b5f09e9ddc6a5f6a569041acc8421; patch: 6.6.145
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 daysPatchlage 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.