{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.12-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  netfs: Fix zeropoint update where i_size \u003e remote_i_size  Fix the update of the zero point[*] by netfs_release_folio() when there is uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio (ie. i_size \u003e remote_i_size).  The update needs to limit zero_point to remote_i_size, not i_size as i_size is a local phenomenon reflecting updates made locally to the pagecache, not stuff written to the server.  remote_i_size tracks the server's i_size.  [*] The zero point is the file position from which we can assume that the     server will just return zeros, so we can avoid generating reads.  Note that netfs_invalidate_folio() probably doesn't need fixing as zero_point should be updated by setattr after truncation or fallocate.  Found with:      fsx -q -N 1000000 -p 10000 -o 128000 -l 600000 \\         /xfstest.test/junk --replay-ops=junk.fsxops  using the following as junk.fsxops:      truncate 0x0 0x1bbae 0x82864     write 0x3ef2e 0xf9c8 0x1bbae     write 0x67e05 0xcb5a 0x4e8f6     mapread 0x57781 0x85b6 0x7495f     copy_range 0x5d3d 0x10329 0x54fac 0x7495f     write 0x64710 0x1c2b 0x7495f     mapread 0x64000 0x1000 0x7495f  on cifs with the default cache option.  It shows read-gaps on folio 0x64 failing with a short read (ie. it hits EOF) if the FMODE_READ check is commented out in netfs_perform_write():                  if (//(file-\u003ef_mode \u0026 FMODE_READ) ||                     netfs_is_cache_enabled(ctx)) {  and no fscache.  This was initially found with the generic/522 xfstest.",
  "id": "DEBIAN-CVE-2026-64159",
  "modified": "2026-09-14T16:47:38.143751231Z",
  "published": "2026-07-19T16:17:57.913Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64159"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-64159"
  ]
}