CVE-2026-23248 (GCVE-0-2026-23248)

Vulnerability from cvelistv5 – Published: 2026-03-18 10:05 – Updated: 2026-05-11 22:03
VLAI
Title
perf/core: Fix refcount bug and potential UAF in perf_mmap
Summary
In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix refcount bug and potential UAF in perf_mmap Syzkaller reported a refcount_t: addition on 0; use-after-free warning in perf_mmap. The issue is caused by a race condition between a failing mmap() setup and a concurrent mmap() on a dependent event (e.g., using output redirection). In perf_mmap(), the ring_buffer (rb) is allocated and assigned to event->rb with the mmap_mutex held. The mutex is then released to perform map_range(). If map_range() fails, perf_mmap_close() is called to clean up. However, since the mutex was dropped, another thread attaching to this event (via inherited events or output redirection) can acquire the mutex, observe the valid event->rb pointer, and attempt to increment its reference count. If the cleanup path has already dropped the reference count to zero, this results in a use-after-free or refcount saturation warning. Fix this by extending the scope of mmap_mutex to cover the map_range() call. This ensures that the ring buffer initialization and mapping (or cleanup on failure) happens atomically effectively, preventing other threads from accessing a half-initialized or dying ring buffer.
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: b709eb872e19a19607bbb6d2975bc264d59735cf , < c27dea9f50ed525facb62ef647dddc4722456e07 (git)
Affected: b709eb872e19a19607bbb6d2975bc264d59735cf , < ac7ecb65af170a7fc193e7bd8be15dac84ec6a56 (git)
Affected: b709eb872e19a19607bbb6d2975bc264d59735cf , < 77de62ad3de3967818c3dbe656b7336ebee461d2 (git)
Create a notification for this product.
Linux Linux Affected: 6.14
Unaffected: 0 , < 6.14 (semver)
Unaffected: 6.18.17 , ≤ 6.18.* (semver)
Unaffected: 6.19.7 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/events/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c27dea9f50ed525facb62ef647dddc4722456e07",
              "status": "affected",
              "version": "b709eb872e19a19607bbb6d2975bc264d59735cf",
              "versionType": "git"
            },
            {
              "lessThan": "ac7ecb65af170a7fc193e7bd8be15dac84ec6a56",
              "status": "affected",
              "version": "b709eb872e19a19607bbb6d2975bc264d59735cf",
              "versionType": "git"
            },
            {
              "lessThan": "77de62ad3de3967818c3dbe656b7336ebee461d2",
              "status": "affected",
              "version": "b709eb872e19a19607bbb6d2975bc264d59735cf",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/events/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.17",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.17",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.7",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf/core: Fix refcount bug and potential UAF in perf_mmap\n\nSyzkaller reported a refcount_t: addition on 0; use-after-free warning\nin perf_mmap.\n\nThe issue is caused by a race condition between a failing mmap() setup\nand a concurrent mmap() on a dependent event (e.g., using output\nredirection).\n\nIn perf_mmap(), the ring_buffer (rb) is allocated and assigned to\nevent-\u003erb with the mmap_mutex held. The mutex is then released to\nperform map_range().\n\nIf map_range() fails, perf_mmap_close() is called to clean up.\nHowever, since the mutex was dropped, another thread attaching to\nthis event (via inherited events or output redirection) can acquire\nthe mutex, observe the valid event-\u003erb pointer, and attempt to\nincrement its reference count. If the cleanup path has already\ndropped the reference count to zero, this results in a\nuse-after-free or refcount saturation warning.\n\nFix this by extending the scope of mmap_mutex to cover the\nmap_range() call. This ensures that the ring buffer initialization\nand mapping (or cleanup on failure) happens atomically effectively,\npreventing other threads from accessing a half-initialized or\ndying ring buffer."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          }
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T22:03:11.269Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c27dea9f50ed525facb62ef647dddc4722456e07"
        },
        {
          "url": "https://git.kernel.org/stable/c/ac7ecb65af170a7fc193e7bd8be15dac84ec6a56"
        },
        {
          "url": "https://git.kernel.org/stable/c/77de62ad3de3967818c3dbe656b7336ebee461d2"
        }
      ],
      "title": "perf/core: Fix refcount bug and potential UAF in perf_mmap",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23248",
    "datePublished": "2026-03-18T10:05:10.070Z",
    "dateReserved": "2026-01-13T15:37:45.989Z",
    "dateUpdated": "2026-05-11T22:03:11.269Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-23248",
      "date": "2026-07-29",
      "epss": "0.0012",
      "percentile": "0.02122"
    },
    "microsoft_vex": {
      "current_release_date": "2026-05-22T01:46:58.000Z",
      "cve": "CVE-2026-23248",
      "id": "msrc_CVE-2026-23248",
      "initial_release_date": "2026-03-02T00:00:00.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "perf/core: Fix refcount bug and potential UAF in perf_mmap",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-23248.json",
      "version": "3"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-23248\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-03-18T11:16:16.863\",\"lastModified\":\"2026-06-17T10:21:11.000\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nperf/core: Fix refcount bug and potential UAF in perf_mmap\\n\\nSyzkaller reported a refcount_t: addition on 0; use-after-free warning\\nin perf_mmap.\\n\\nThe issue is caused by a race condition between a failing mmap() setup\\nand a concurrent mmap() on a dependent event (e.g., using output\\nredirection).\\n\\nIn perf_mmap(), the ring_buffer (rb) is allocated and assigned to\\nevent-\u003erb with the mmap_mutex held. The mutex is then released to\\nperform map_range().\\n\\nIf map_range() fails, perf_mmap_close() is called to clean up.\\nHowever, since the mutex was dropped, another thread attaching to\\nthis event (via inherited events or output redirection) can acquire\\nthe mutex, observe the valid event-\u003erb pointer, and attempt to\\nincrement its reference count. If the cleanup path has already\\ndropped the reference count to zero, this results in a\\nuse-after-free or refcount saturation warning.\\n\\nFix this by extending the scope of mmap_mutex to cover the\\nmap_range() call. This ensures that the ring buffer initialization\\nand mapping (or cleanup on failure) happens atomically effectively,\\npreventing other threads from accessing a half-initialized or\\ndying ring buffer.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\\n\\nperf/core: Correcci\u00f3n de error de conteo de referencias y potencial UAF en perf_mmap\\n\\nSyzkaller inform\u00f3 una advertencia de refcount_t: adici\u00f3n en 0; uso despu\u00e9s de liberaci\u00f3n en perf_mmap.\\n\\nEl problema es causado por una condici\u00f3n de carrera entre una configuraci\u00f3n de mmap() fallida y un mmap() concurrente en un evento dependiente (por ejemplo, usando redirecci\u00f3n de salida).\\n\\nEn perf_mmap(), el ring_buffer (rb) se asigna y se establece en event-\u0026gt;rb con el mmap_mutex retenido. El mutex es entonces liberado para realizar map_range().\\n\\nSi map_range() falla, se llama a perf_mmap_close() para limpiar. Sin embargo, dado que el mutex fue liberado, otro hilo que se adjunta a este evento (a trav\u00e9s de eventos heredados o redirecci\u00f3n de salida) puede adquirir el mutex, observar el puntero event-\u0026gt;rb v\u00e1lido e intentar incrementar su conteo de referencias. Si la ruta de limpieza ya ha reducido el conteo de referencias a cero, esto resulta en un uso despu\u00e9s de liberaci\u00f3n o una advertencia de saturaci\u00f3n de conteo de referencias.\\n\\nEsto se corrige al extender el alcance de mmap_mutex para cubrir la llamada a map_range(). Esto asegura que la inicializaci\u00f3n y el mapeo del b\u00fafer de anillo (o la limpieza en caso de fallo) ocurra de manera at\u00f3mica y efectiva, evitando que otros hilos accedan a un b\u00fafer de anillo medio inicializado o en proceso de terminaci\u00f3n.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"kernel/events/core.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"b709eb872e19a19607bbb6d2975bc264d59735cf\",\"lessThan\":\"c27dea9f50ed525facb62ef647dddc4722456e07\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"b709eb872e19a19607bbb6d2975bc264d59735cf\",\"lessThan\":\"ac7ecb65af170a7fc193e7bd8be15dac84ec6a56\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"b709eb872e19a19607bbb6d2975bc264d59735cf\",\"lessThan\":\"77de62ad3de3967818c3dbe656b7336ebee461d2\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"kernel/events/core.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.14\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.14\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.17\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.19.7\",\"lessThanOrEqual\":\"6.19.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.0\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-416\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.14\",\"versionEndExcluding\":\"6.18.17\",\"matchCriteriaId\":\"E367EC2E-72DB-4555-9BE2-A5B9C97AD4E6\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.19\",\"versionEndExcluding\":\"6.19.7\",\"matchCriteriaId\":\"69245D10-0B71-485E-80C3-A64F077004D3\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"F253B622-8837-4245-BCE5-A7BF8FC76A16\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/77de62ad3de3967818c3dbe656b7336ebee461d2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ac7ecb65af170a7fc193e7bd8be15dac84ec6a56\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c27dea9f50ed525facb62ef647dddc4722456e07\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-07-02T17:12:20+00:00",
      "cve": "CVE-2026-23248",
      "id": "CVE-2026-23248",
      "initial_release_date": "2026-03-18T00:00:00+00:00",
      "product_status:known_affected": "274",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: perf/core: Fix refcount bug and potential UAF in perf_mmap",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23248.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "important",
      "current_release_date": "2026-07-15T05:30:54Z",
      "cve": "CVE-2026-23248",
      "id": "CVE-2026-23248",
      "initial_release_date": "2026-03-19T00:27:14Z",
      "product_status:known_affected": "22",
      "product_status:known_not_affected": "299",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-23248",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-23248.json",
      "version": "10"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.