Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80807nilfs2: reject invalid block index in GC ioctl

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < 898404cdf882d7b54f1132f75570984ca3214796
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < ba8a8b563a28d358c45c62a306d421434a058648
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < 3bd064ccc70b85f9a3d53aece29dc8473be5a226
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < a5e776e2937581d67ec5b9b4d27b0f70d7baa6b1
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < 68aa9ab6f8f2895713aa6ddf781463ed8ea5ba44
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < e447f7edb99bd00cec63d6f3049e2e5074946f71
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < ec6ddf271dfa4c7e3147bc2c8b2bad4315f316a1
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < fbcfb75c20d71a5b542ad4ac3b79d10b997c8152
    • affected 7942b919f7321f95a777d396ff7894a7a83dc9b0 – < a1735eae55448bc79c2da6593455791e886f6ed8
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 5.10.269 – ≤ 5.10.*
    • unaffected 5.15.220 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80807 badge
[![CVE-2026-80807](https://cveledger.app/badge/CVE-2026-80807.svg)](https://cveledger.app/cve/CVE-2026-80807)

Record last updated .