{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.94-1"
            }
          ],
          "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 folio-\u003eprivate handling in netfs_perform_write()  Under some circumstances, netfs_perform_write() doesn't correctly manipulate folio-\u003eprivate between NULL, NETFS_FOLIO_COPY_TO_CACHE, pointing to a group and pointing to a netfs_folio struct, leading to potential multiple attachments of private data with associated folio ref leaks and also leaks of netfs_folio structs or netfs_group refs.  Fix this by consolidating the place at which a folio is marked uptodate in one place and having that look at what's attached to folio-\u003eprivate and decide how to clean it up and then set the new group.  Also, the content shouldn't be flushed if group is NULL, even if a group is specified in the netfs_group parameter, as that would be the case for a new folio.  A filesystem should always specify netfs_group or never specify netfs_group.  The Sashiko auto-review tool noted that it was theoretically possible that the fpos \u003e= ctx-\u003ezero_point section might leak if it modified a streaming write folio.  This is unlikely, but with a network filesystem, third party changes can happen.  It also pointed out that __netfs_set_group() would leak if called multiple times on the same folio from the \"whole folio modify section\".",
  "id": "DEBIAN-CVE-2026-64059",
  "modified": "2026-09-14T16:47:44.113686639Z",
  "published": "2026-07-19T16:17:46.407Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64059"
    }
  ],
  "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-64059"
  ]
}