CVE-2026-89640
CVE CVE-2026-89640EUVD EUVD-2026-76552Published 2026-09-11T19:45:33.000ZLast changed 2026-09-14T12:01:42.000ZCVSS 7.1
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 With len == 0 (clone to EOF), the effective length is computed as: len = src_inode->i_size - off; If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range(). The existing off >= i_size check fires only after the ioctl has already been sent. Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk. Reject off > src_size with -EINVAL. Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().
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.3-rc1; 4.5; 04b38d601239b4d9be641b412cf4b7456a041c67 <b098f5e5858797827666e6cd73033f52fc39b5f6; patch: 6.18.50; 04b38d601239b4d9be641b412cf4b7456a041c67 <f3d1ae1e6bc4a9f559185b6e7bd2b6375ec2fdd4; patch: 6.6.157; 04b38d601239b4d9be641b412cf4b7456a041c67 <c2a0dcb5a7a1516aa6eb6d5cedca6a8e76527028; 04b38d601239b4d9be641b412cf4b7456a041c67 <6c322f5cf7476ded7a9a20f7be72462065a03c68; 04b38d601239b4d9be641b412cf4b7456a041c67 <b057ca17b656345d04669cb87f2aff9b31d873db; patch: 6.12.109; 04b38d601239b4d9be641b412cf4b7456a041c67 <7f62817fe049b0f3652518c1ba72631ec1e0a322; patch: 7.2.4; patch: 6.1.188; 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 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.