{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-53518",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-53518"
  ],
  "published": "2025-10-01T11:50:00Z",
  "summary": "PM / devfreq: Fix leak in devfreq_dev_release()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nPM / devfreq: Fix leak in devfreq_dev_release()\n\nsrcu_init_notifier_head() allocates resources that need to be released\nwith a srcu_cleanup_notifier_head() call.\n\nReported by kmemleak.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.53",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-53518"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7462483446cb9986568ad7adae746ce5f18d2968"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/64e6e0dc2d578c0a9e31cb4edd719f0a3ed98f6d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/29811f4b8255d4238cf326f3bb7129784766beab"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ab192e5e5d3b48415909a8408acfd007a607bcc0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/111bafa210ae546bee7644be730c42df9c35b66e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8918025feb2f5f7c73f2495c158f22997e25cb02"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1640e9c72173911ad0fddb05012c01eafe082c4e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3354c401c68d70567d1ef25d12f4e22a7813a3c6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5693d077595de721f9ddbf9d37f40e5409707dfe"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:24:39Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The devfreq release path is reached only through local device-lifecycle operations \u2014 driver bind/unbind via sysfs, module load/unload, or a failed probe \u2014 with no remote or network-facing consumer of this code. There is no packet-driven or adjacent-network path into devfreq_dev_release().\nAC:L - The leak is deterministic \u2014 every devfreq device teardown unconditionally drops the srcu per-CPU allocations, so a repeated unbind/rebind loop reliably exhausts per-CPU memory. The attacker drives both the srcu grace-period activity (governor/notifier teardown) and the immediately following kfree(), so the dangling-work window is attacker-created rather than dependent on external state.\nPR:L - The trigger is a local device-management operation on the affected platform (GPU/UFS/bus devfreq drivers), consistent with how other driver teardown/unload memory-corruption issues are scored; no authentication to a remote service and no capability that is unreachable in practice on the affected embedded/Android deployments is needed.\nUI:N - The attacker performs the bind/unbind or module unload themselves in a loop; no victim action, mount, or file open is required for the leak or the dangling srcu work to occur.\nS:U - The leaked allocations and any resulting corruption are entirely within the kernel's own memory and security authority, with no crossing into a hypervisor, IOMMU, or other security domain.\nC:H - kfree()ing the devfreq object while the srcu_struct is still live leaves leaked per-CPU srcu_data with dangling ->ssp pointers and pending srcu work into freed slab memory, a use-after-free that can be groomed to read back kernel data from the reallocated object.\nI:H - The uncleaned srcu_struct embeds a delayed_work and per-CPU timers that can fire after the containing allocation is freed, causing srcu state-machine writes (locks, sequence counters, work_struct/timer list links) into memory an attacker can reallocate \u2014 a write primitive into a controlled heap object.\nA:H - Each teardown leaks srcu_usage, the srcu_node tree, and a per-CPU srcu_data array; per-CPU memory is a scarce vmalloc-backed resource, so repeated cycles exhaust it and cause system-wide allocation failures, and the dangling timer/work references can additionally oops the kernel."
    }
  }
}