dm: dm-crypt: Do not partially accept write BIOs with zoned targets

{
  "id": "17f379c852520cffa48dd4e2463b6eee9c542621fc72660b194f5853e1a8229a",
  "url": "https://osv.dev/vulnerability/CVE-2025-39791",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "dm: dm-crypt: Do not partially accept write BIOs with zoned targets",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: dm: dm-crypt: Do not partially accept write BIOs with zoned targets Read and write operations issued to a dm-crypt target may be split according to the dm-crypt internal limits defined by the max_read_size and max_write_size module parameters (default is 128 KB). The intent is to improve processing time of large BIOs by splitting them into smaller operations that can be parallelized on different CPUs. For zoned dm-crypt targets, this BIO splitting is still done but without the parallel execution to ensure that the issuing order of write operations to the underlying devices remains sequential. However, the splitting itself causes other problems: 1) Since dm-crypt relies on the block layer zone write plugging to handle zone append emulation using regular write operations, the reminder of a split write BIO will always be plugged into the target zone write plugged. Once the on-going write BIO finishes, this reminder BIO is unplugged and issued from the zone write plug work. If this reminder BIO itself needs to be split, the reminder will be re-issued and plugged again, but that causes a call to a blk_queue_enter(), which may block if a queue freeze operation was initiated. This results in a deadlock as DM submission still holds BIOs that the queue freeze side is waiting for. 2) dm-crypt relies on the emulation done by the block layer using regular write operations for processing zone append operations. This still",
    "evidence": "osv:CVE-2025-39791",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.12.44",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.16.4",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-39791",
      "aliases": [
        "CVE-2025-39791"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "f211268ed1f9bdf48f06a3ead5f5d88437450579"
                },
                {
                  "fixed": "8864616719b6bbf92356bc89ff544b0cd484c656"
                },
                {
                  "fixed": "52a2c4c60470352acf9cde7a2dfa661c1e67e796"
                },
                {
                  "fixed": "e549663849e5bb3b985dc2d293069f0d9747ae72"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39791.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.10.0"
                },
                {
                  "fixed": "6.12.44"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.16.4"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39791.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:31.523130664Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/52a2c4c60470352acf9cde7a2dfa661c1e67e796",
        "https://git.kernel.org/stable/c/8864616719b6bbf92356bc89ff544b0cd484c656",
        "https://git.kernel.org/stable/c/e549663849e5bb3b985dc2d293069f0d9747ae72",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39791.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-39791",
        "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/2025/39xxx/CVE-2025-39791.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-39791",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 498693,
  "published_at": "2025-09-11T16:56:39.397+00:00"
}