CVE-2026-89490
CVE CVE-2026-89490EUVD EUVD-2026-76396Published 2026-09-11T19:43:42.000ZLast changed 2026-09-14T12:00:25.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix readdir position truncation on 32-bit kernels In ocfs2_dir_foreach_blk_el(), the directory cookie position is rebuilt with ctx->pos = (ctx->pos & ~(sb->s_blocksize - 1)) | offset; `ctx->pos` is loff_t (signed 64-bit), while `sb->s_blocksize` is unsigned long. On 32-bit kernels unsigned long is 32-bit, so the mask ~(sb->s_blocksize - 1) is computed as a 32-bit unsigned value (e.g. 0xfffff000 for a 4 KiB block size). In the AND expression with the 64-bit `ctx->pos`, that unsigned operand is zero-extended to 64 bits per the usual arithmetic conversions, yielding 0x00000000fffff000. The high 32 bits of `ctx->pos` are silently cleared, even though directory size is allowed to exceed 4 GiB. When readdir() crosses the 4 GiB boundary on a 32-bit kernel the position is reset back into the first 4 GiB block, making the re-validation path re-enumerate already-returned dirents indefinitely. This is ocfs2_dir_foreach_blk_el(), the extent-list readdir path taken for all non-inline directories, so a directory large enough to cross 4 GiB reaches it. This is the same class of bug that commit 3dce5bb82c97 ("exfat: Fix bitwise operation having different size") fixed in exfat, and the fix mirrors the equivalent ext4 fix in this series. Cast the operand to loff_t so the mask is 64-bit before the AND: ctx->pos = (ctx->pos & ~((loff_t)sb->s_blocksize - 1)) | offset; 64-bit kernels are unaffected.
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 ccd979bdbce9fba8412beb3f1de68a9d0171b12c <b53e2b271eeb6040c2a4a78230c570dc41cdcfa4; ccd979bdbce9fba8412beb3f1de68a9d0171b12c <94569154ba49f5f85645d2019c8e206213d8404e; ccd979bdbce9fba8412beb3f1de68a9d0171b12c <f9dd5cad8d09110ddff2db1fe756aae93c7552ff; patch: 6.12.109; ccd979bdbce9fba8412beb3f1de68a9d0171b12c <1ae7029823ae4c91664cb32eec7fb8dd5e1a337a; patch: 6.18.50; patch: 7.2.4; 2.6.16; patch: 5.15.221; patch: 0; patch: 5.10.270; patch: 7.3-rc1; ccd979bdbce9fba8412beb3f1de68a9d0171b12c <c28dc3407937aa8f225942538cd585c9b28ea65a; patch: 6.6.157; ccd979bdbce9fba8412beb3f1de68a9d0171b12c <c0c165487a2ea5a37ddcdab4259157b7a527129c; ccd979bdbce9fba8412beb3f1de68a9d0171b12c <1001fb3b69a11eaa0dc7c7428f6edfa48b88997a; patch: 6.1.188; ccd979bdbce9fba8412beb3f1de68a9d0171b12c <a63308ab426f3a3c7e33b02c150ea59054620261
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.