CVE-2026-64187

CVE CVE-2026-64187EUVD EUVD-2026-46007Published 2026-07-20T16:27:46.000ZLast changed 2026-07-24T14:34:17.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: xfs: fail recovery on a committed log item with no regions If the first op of a transaction is a bare transaction header (len == sizeof(struct xfs_trans_header)), xlog_recover_add_to_trans() adds an item but no region, leaving it on r_itemq with ri_cnt == 0 and ri_buf == NULL. The header can be split across op records, so later ops may still add regions; the item is only invalid if the transaction commits with none. The runtime commit path never emits such a transaction, so this only happens on a crafted log. It came from an AI-assisted code audit of the recovery parser. xlog_recover_reorder_trans() calls ITEM_TYPE() on the item, which reads *(unsigned short *)item->ri_buf[0].iov_base and faults on the NULL ri_buf. Reject it there, before the commit handlers that also read ri_buf[0]. KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:xlog_recover_reorder_trans (fs/xfs/xfs_log_recover.c:1836) xlog_recover_commit_trans (fs/xfs/xfs_log_recover.c:2043) xlog_recover_process_data (fs/xfs/xfs_log_recover.c:2501) xlog_do_recovery_pass (fs/xfs/xfs_log_recover.c:3244) xlog_recover (fs/xfs/xfs_log_recover.c:3493) xfs_log_mount (fs/xfs/xfs_log.c:618) xfs_mountfs (fs/xfs/xfs_mount.c:1034) xfs_fs_fill_super (fs/xfs/xfs_super.c:1938) vfs_get_tree (fs/super.c:1695) path_mount (fs/namespace.c:4161) __x64_sys_mount (fs/namespace.c:4367)

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 89cebc8477290b152618ffa110bbeae340d50900 <2094dab19d45c487285617b7b68913d0cc0c1211; patch: 7.2-rc4; patch: 0; patch: 6.18.39; patch: 7.1.4; 4.3; 89cebc8477290b152618ffa110bbeae340d50900 <226a3c8bea7163c39fe0a1c0ffc7ab7410ef3ba4; 89cebc8477290b152618ffa110bbeae340d50900 <d50b1fd066d66ceb548ba43e332cfe8a47e5e55a; patch: 5.15.212; 89cebc8477290b152618ffa110bbeae340d50900 <cccbabeb9a18fcb978d76d6047f2b59214aa7749; patch: 6.6.145; patch: 6.1.178; 89cebc8477290b152618ffa110bbeae340d50900 <d98f22d2e11e0a36493aeb25b2933571ee90d9a4; patch: 6.12.96; 89cebc8477290b152618ffa110bbeae340d50900 <d0ae7ec3aa61db5140b107f0a63e017f63e56a96; 89cebc8477290b152618ffa110bbeae340d50900 <5105426424ad6981db827cc1ada835a488fab035

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.