CVE-2026-64265

CVE CVE-2026-64265EUVD EUVD-2026-48977Published 2026-07-25T08:49:14.000ZLast changed 2026-08-05T12:40:23.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req When fuse_resend() moves a request from fpq->processing back to fiq->pending, it sets FR_PENDING and clears FR_SENT but does not remove the requests intr_entry from fiq->interrupts. If the request had FR_INTERRUPTED set from a prior signal, intr_entry remains dangling on fiq->interrupts. When the requesting task then receives a fatal signal, fuse_remove_pending_req() sees FR_PENDING=1, removes the request from fiq->pending and frees it via the refcount path, also without cleaning intr_entry. The stale intr_entry causes use-after-free when fuse_read_interrupt() iterates fiq->interrupts: - list_del_init(&req->intr_entry) -> UAF write on freed slab - req->in.h.unique -> UAF read, data leaked to userspace Remove intr_entry from fiq->interrupts in fuse_resend() for interrupted requests before they are placed back on fiq->pending. Add a WARN_ON if the intr_entry is not empty on request destruction.

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.4; patch: 6.12.96; patch: 7.2-rc1; patch: 6.18.39; 760eac73f9f69aa28fcb3050b4946c2dcc656d12 <893479015cb6442fd389d3b553ab3036c9541715; 6.9; 760eac73f9f69aa28fcb3050b4946c2dcc656d12 <f8fce75fedf73ac72aa09163deb8f4291fdcaad2; 760eac73f9f69aa28fcb3050b4946c2dcc656d12 <1d8ecd0cd696a5df0b2f72046a4ccee5d2a8ec2c; 760eac73f9f69aa28fcb3050b4946c2dcc656d12 <7366e6f4d2b4c7002b13fb01219e83679dad4127; patch: 0

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.