Skip to content
Heist/ feed
Back to feed
UnratedFix available

btrfs: zlib: fix the folio leak on S390 hardware acceleration

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: btrfs: zlib: fix the folio leak on S390 hardware acceleration [BUG] After commit aa60fe12b4f4 ("btrfs: zlib: refactor S390x HW acceleration buffer preparation"), we no longer release the folio of the page cache of folio returned by btrfs_compress_filemap_get_folio() for S390 hardware acceleration path. [CAUSE] Before that commit, we call kumap_local() and folio_put() after handling each folio. Although the timing is not ideal (it release previous folio at the beginning of the loop, and rely on some extra cleanup out of the loop), it at least handles the folio release correctly. Meanwhile the refactored code is easier to read, it lacks the call to release the filemap folio. [FIX] Add the missing folio_put() for copy_data_into_buffer().

Products
Kernel
Affected versions
Not specified
Fixed versions
6.18.9
CVEs
CVE-2026-23147
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 08:42 UTC · Revision 1

Source evidence

btrfs: zlib: fix the folio leak on S390 hardware acceleration

core-osv · Original source

Published 14 Feb 2026, 16:01 UTC

In the Linux kernel, the following vulnerability has been resolved: btrfs: zlib: fix the folio leak on S390 hardware acceleration [BUG] After commit aa60fe12b4f4 ("btrfs: zlib: refactor S390x HW acceleration buffer preparation"), we no longer release the folio of the page cache of folio returned by btrfs_compress_filemap_get_folio() for S390 hardware acceleration path. [CAUSE] Before that commit, we call kumap_local() and folio_put() after handling each folio. Although the timing is not ideal (it release previous folio at the beginning of the loop, and rely on some extra cleanup out of the loop), it at least handles the folio release correctly. Meanwhile the refactored code is easier to read, it lacks the call to release the filemap folio. [FIX] Add the missing folio_put() for copy_data_into_buffer().

osv:CVE-2026-23147

Kernel

Fixed versions: 6.18.9

Complete source record
{
  "id": "b007f254885248e157a2250085a911426982395f9fe6045f8508dc8bb432060c",
  "url": "https://osv.dev/vulnerability/CVE-2026-23147",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "btrfs: zlib: fix the folio leak on S390 hardware acceleration",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: btrfs: zlib: fix the folio leak on S390 hardware acceleration [BUG] After commit aa60fe12b4f4 (\"btrfs: zlib: refactor S390x HW acceleration buffer preparation\"), we no longer release the folio of the page cache of folio returned by btrfs_compress_filemap_get_folio() for S390 hardware acceleration path. [CAUSE] Before that commit, we call kumap_local() and folio_put() after handling each folio. Although the timing is not ideal (it release previous folio at the beginning of the loop, and rely on some extra cleanup out of the loop), it at least handles the folio release correctly. Meanwhile the refactored code is easier to read, it lacks the call to release the filemap folio. [FIX] Add the missing folio_put() for copy_data_into_buffer().",
    "evidence": "osv:CVE-2026-23147",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.9",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-23147",
      "aliases": [
        "CVE-2026-23147"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "aa60fe12b4f49f49fc73e5023f8675e2df1f7805"
                },
                {
                  "fixed": "e80617a5e1c246da2f112a1a072cdd535046adfe"
                },
                {
                  "fixed": "0d0f1314e8f86f5205f71f9e31e272a1d008e40b"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23147.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.15.0"
                },
                {
                  "fixed": "6.18.9"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23147.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:34.251657942Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/0d0f1314e8f86f5205f71f9e31e272a1d008e40b",
        "https://git.kernel.org/stable/c/e80617a5e1c246da2f112a1a072cdd535046adfe",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23147.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-23147",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23147.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-23147",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 501218,
  "published_at": "2026-02-14T16:01:16.917+00:00"
}