CVE-2026-80807
Vulnérabilité non évaluée dans Linux (Linux)
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject invalid block index in GC ioctl Syzbot reported list corruption caused by a double list_add_tail() call on bh->b_assoc_buffers within nilfs_lookup_dirty_data_buffers(). Analysis revealed that the root cause was the insertion of a page/folio with a page index of ULONG_MAX into the page cache via the GC ioctl. filemap_get_folios_tag(), called by nilfs_lookup_dirty_data_buffers(), repeatedly detects a dirty folio with a page index of ULONG_MAX due to index wrap-around, leading to duplicate processing of dirty buffers. As a preparatory step, the GC ioctl loads the page/folio of the block to be moved during GC and inserts it into the page cache based on information in the nilfs_vdesc structure passed as an argument. Normally, this does not cause issues because the user-space GC library configures the nilfs_vdesc structure properly. However, since there is no range check on the parameters determining the page index, a request with artificially crafted parameters -- such as those generated by Syzbot -- can result in a page/folio being inserted with a page index of ULONG_MAX, triggering the above problem. This resolves the issue by checking the ranges of 'vd_offset' and 'vd_vblocknr' in the nilfs_vdesc structure that determine the page index, thereby preventing the invalid page/folio insertions.
Gravité et risque d'exploitation
CVE-2026-80807 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.20 %, ce qui la place devant 9.3 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions 7.2.1, <=6.1.*, 7.1.11, <=6.12.*, 6.6.156, 5.10.269, 0, <=7.1.*, <898404cdf882d7b54f1132f75570984ca3214796, <fbcfb75c20d71a5b542ad4ac3b79d10b997c8152, <ba8a8b563a28d358c45c62a306d421434a058648, <ec6ddf271dfa4c7e3147bc2c8b2bad4315f316a1, <=5.10.*, 2.6.30, <=6.6.*, <a5e776e2937581d67ec5b9b4d27b0f70d7baa6b1, <3bd064ccc70b85f9a3d53aece29dc8473be5a226, <2.6.30, <68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44, <=6.18.*, <e447f7edb99bd00cec63d6f3049e2e5074946f71, 6.18.47, <=7.2.*, <a1735eae55448bc79c2da6593455791e886f6ed8, 5.15.220, <=*, <=5.15.*, 6.12.108, 7942b919f7321f95a777d396ff7894a7a83dc9b0, 6.1.187, 7.3) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- https://git.kernel.org/stable/c/898404cdf882d7b54f1132f75570984ca3214796
- https://git.kernel.org/stable/c/ba8a8b563a28d358c45c62a306d421434a058648
- https://git.kernel.org/stable/c/3bd064ccc70b85f9a3d53aece29dc8473be5a226
- https://git.kernel.org/stable/c/a5e776e2937581d67ec5b9b4d27b0f70d7baa6b1
- https://git.kernel.org/stable/c/68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44
- https://git.kernel.org/stable/c/e447f7edb99bd00cec63d6f3049e2e5074946f71
- https://git.kernel.org/stable/c/ec6ddf271dfa4c7e3147bc2c8b2bad4315f316a1
- https://git.kernel.org/stable/c/fbcfb75c20d71a5b542ad4ac3b79d10b997c8152
- https://git.kernel.org/stable/c/a1735eae55448bc79c2da6593455791e886f6ed8
