tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case

{
  "id": "a892c10f0d0ec2d569609aa3bdf440458cdfb57d1eb7c092b6e40189aef1d14b",
  "url": "https://osv.dev/vulnerability/CVE-2022-48819",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case syzbot found that mixing sendpage() and sendmsg(MSG_ZEROCOPY) calls over the same TCP socket would again trigger the infamous warning in inet_sock_destruct() WARN_ON(sk_forward_alloc_get(sk)); While Talal took into account a mix of regular copied data and MSG_ZEROCOPY one in the same skb, the sendpage() path has been forgotten. We want the charging to happen for sendpage(), because pages could be coming from a pipe. What is missing is the downgrading of pure zerocopy status to make sure sk_forward_alloc will stay synced. Add tcp_downgrade_zcopy_pure() helper so that we can use it from the two callers.",
    "evidence": "osv:CVE-2022-48819",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.16.10",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2022-48819",
      "aliases": [
        "CVE-2022-48819"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "9b65b17db72313b7a4fe9bc9502928c88be57986"
                },
                {
                  "fixed": "47f3860c4931175f112f28dcac66eacca9b1040f"
                },
                {
                  "fixed": "f8d9d938514f46c4892aff6bfe32f425e84d81cc"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48819.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "5.16.10"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48819.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:31.956048905Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/47f3860c4931175f112f28dcac66eacca9b1040f",
        "https://git.kernel.org/stable/c/f8d9d938514f46c4892aff6bfe32f425e84d81cc",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48819.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-48819",
        "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/2022/48xxx/CVE-2022-48819.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-48819",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 498822,
  "published_at": "2024-07-16T11:44:06.619+00:00"
}