Answer in brief
CVE-2026-64532 records a Unknown severity vulnerability in fs/ntfs3: bound NTFS_DE view.data_off in UpdateRecordData{Root,Allocation}. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64532 records a Unknown severity vulnerability in fs/ntfs3: bound NTFS_DE view.data_off in UpdateRecordData{Root,Allocation}. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b46acd6a6a627d876898e1c84d3f84902264b445 <b20e5a709d8bd190d6e4645606763c7423e694c1 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <d41b382068ca4e64e421f736cdd700095464b6ac || >=b46acd6a6a627d876898e1c84d3f84902264b445 <429d653ca641d38a78609b8f62e81a0a5c780a2d || >=b46acd6a6a627d876898e1c84d3f84902264b445 <315d3a9a48b49f889da3d858a9307e677cb9e1bd || >=b46acd6a6a627d876898e1c84d3f84902264b445 <be306b8d9143a9c076c804a7ca025d69caf9c448 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <36feda687afebae24c472202694448738809c411 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <3e127829e57f5190f612412ece4541cb96d5ec7a | b20e5a709d8bd190d6e4645606763c7423e694c1, d41b382068ca4e64e421f736cdd700095464b6ac, 429d653ca641d38a78609b8f62e81a0a5c780a2d, 315d3a9a48b49f889da3d858a9307e677cb9e1bd, be306b8d9143a9c076c804a7ca025d69caf9c448, 36feda687afebae24c472202694448738809c411, 3e127829e57f5190f612412ece4541cb96d5ec7a |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Jul 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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" (<[email protected]>) which proposes calling ntfs3_bad_de_range(); that helper does not exist in mainline. This patch uses inline checks.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b46acd6a6a627d876898e1c84d3f84902264b445 <b20e5a709d8bd190d6e4645606763c7423e694c1 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <d41b382068ca4e64e421f736cdd700095464b6ac || >=b46acd6a6a627d876898e1c84d3f84902264b445 <429d653ca641d38a78609b8f62e81a0a5c780a2d || >=b46acd6a6a627d876898e1c84d3f84902264b445 <315d3a9a48b49f889da3d858a9307e677cb9e1bd || >=b46acd6a6a627d876898e1c84d3f84902264b445 <be306b8d9143a9c076c804a7ca025d69caf9c448 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <36feda687afebae24c472202694448738809c411 || >=b46acd6a6a627d876898e1c84d3f84902264b445 <3e127829e57f5190f612412ece4541cb96d5ec7a | b20e5a709d8bd190d6e4645606763c7423e694c1, d41b382068ca4e64e421f736cdd700095464b6ac, 429d653ca641d38a78609b8f62e81a0a5c780a2d, 315d3a9a48b49f889da3d858a9307e677cb9e1bd, be306b8d9143a9c076c804a7ca025d69caf9c448, 36feda687afebae24c472202694448738809c411, 3e127829e57f5190f612412ece4541cb96d5ec7a |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Jul 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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" (<[email protected]>) which proposes calling ntfs3_bad_de_range(); that helper does not exist in mainline. This patch uses inline checks.
Quoted source text, attributed separately from HOL analysis.