CVE-2023-53698 (GCVE-0-2023-53698)
Vulnerability from cvelistv5
Published
2025-10-22 13:23
Modified
2025-10-22 13:23
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: xsk: fix refcount underflow in error path Fix a refcount underflow problem reported by syzbot that can happen when a system is running out of memory. If xp_alloc_tx_descs() fails, and it can only fail due to not having enough memory, then the error path is triggered. In this error path, the refcount of the pool is decremented as it has incremented before. However, the reference to the pool in the socket was not nulled. This means that when the socket is closed later, the socket teardown logic will think that there is a pool attached to the socket and try to decrease the refcount again, leading to a refcount underflow. I chose this fix as it involved adding just a single line. Another option would have been to move xp_get_pool() and the assignment of xs->pool to after the if-statement and using xs_umem->pool instead of xs->pool in the whole if-statement resulting in somewhat simpler code, but this would have led to much more churn in the code base perhaps making it harder to backport.
References
Impacted products
Vendor Product Version
Linux Linux Version: f7019562f142bc041f9cde63af338d1886585923
Version: ba3beec2ec1d3b4fd8672ca6e781dac4b3267f6e
Version: ba3beec2ec1d3b4fd8672ca6e781dac4b3267f6e
Version: ba3beec2ec1d3b4fd8672ca6e781dac4b3267f6e
Version: 9f0c8a9d4ef1b9ebee0e4ac2495fe790727044aa
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/xdp/xsk.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "789fcd94c9cac133dd4d96e193188661aca9f6c3",
              "status": "affected",
              "version": "f7019562f142bc041f9cde63af338d1886585923",
              "versionType": "git"
            },
            {
              "lessThan": "15b453cf7348973217558235b9ece2ee5fea6777",
              "status": "affected",
              "version": "ba3beec2ec1d3b4fd8672ca6e781dac4b3267f6e",
              "versionType": "git"
            },
            {
              "lessThan": "3e7722c31d4167eb7f3ffd35aba52cab69b79072",
              "status": "affected",
              "version": "ba3beec2ec1d3b4fd8672ca6e781dac4b3267f6e",
              "versionType": "git"
            },
            {
              "lessThan": "85c2c79a07302fe68a1ad5cc449458cc559e314d",
              "status": "affected",
              "version": "ba3beec2ec1d3b4fd8672ca6e781dac4b3267f6e",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "9f0c8a9d4ef1b9ebee0e4ac2495fe790727044aa",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/xdp/xsk.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.18"
            },
            {
              "lessThan": "5.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.127",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.46",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.4.*",
              "status": "unaffected",
              "version": "6.4.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.5",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.127",
                  "versionStartIncluding": "5.15.47",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.46",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.4.11",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.5",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.17.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxsk: fix refcount underflow in error path\n\nFix a refcount underflow problem reported by syzbot that can happen\nwhen a system is running out of memory. If xp_alloc_tx_descs() fails,\nand it can only fail due to not having enough memory, then the error\npath is triggered. In this error path, the refcount of the pool is\ndecremented as it has incremented before. However, the reference to\nthe pool in the socket was not nulled. This means that when the socket\nis closed later, the socket teardown logic will think that there is a\npool attached to the socket and try to decrease the refcount again,\nleading to a refcount underflow.\n\nI chose this fix as it involved adding just a single line. Another\noption would have been to move xp_get_pool() and the assignment of\nxs-\u003epool to after the if-statement and using xs_umem-\u003epool instead of\nxs-\u003epool in the whole if-statement resulting in somewhat simpler code,\nbut this would have led to much more churn in the code base perhaps\nmaking it harder to backport."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-10-22T13:23:38.384Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/789fcd94c9cac133dd4d96e193188661aca9f6c3"
        },
        {
          "url": "https://git.kernel.org/stable/c/15b453cf7348973217558235b9ece2ee5fea6777"
        },
        {
          "url": "https://git.kernel.org/stable/c/3e7722c31d4167eb7f3ffd35aba52cab69b79072"
        },
        {
          "url": "https://git.kernel.org/stable/c/85c2c79a07302fe68a1ad5cc449458cc559e314d"
        }
      ],
      "title": "xsk: fix refcount underflow in error path",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53698",
    "datePublished": "2025-10-22T13:23:38.384Z",
    "dateReserved": "2025-10-22T13:21:37.345Z",
    "dateUpdated": "2025-10-22T13:23:38.384Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-53698\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-10-22T14:15:44.330\",\"lastModified\":\"2025-10-22T21:12:48.953\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nxsk: fix refcount underflow in error path\\n\\nFix a refcount underflow problem reported by syzbot that can happen\\nwhen a system is running out of memory. If xp_alloc_tx_descs() fails,\\nand it can only fail due to not having enough memory, then the error\\npath is triggered. In this error path, the refcount of the pool is\\ndecremented as it has incremented before. However, the reference to\\nthe pool in the socket was not nulled. This means that when the socket\\nis closed later, the socket teardown logic will think that there is a\\npool attached to the socket and try to decrease the refcount again,\\nleading to a refcount underflow.\\n\\nI chose this fix as it involved adding just a single line. Another\\noption would have been to move xp_get_pool() and the assignment of\\nxs-\u003epool to after the if-statement and using xs_umem-\u003epool instead of\\nxs-\u003epool in the whole if-statement resulting in somewhat simpler code,\\nbut this would have led to much more churn in the code base perhaps\\nmaking it harder to backport.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/15b453cf7348973217558235b9ece2ee5fea6777\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/3e7722c31d4167eb7f3ffd35aba52cab69b79072\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/789fcd94c9cac133dd4d96e193188661aca9f6c3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/85c2c79a07302fe68a1ad5cc449458cc559e314d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.