dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53065

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.10.258 / 5.15.209 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: ASoC: sti: use managed regmap_field allocations The regmap_field objects allocated at player init are never freed and may leak resources if the driver is removed. Switch to devm_regmap_field_alloc() to automatically limit the lifetime of the allocations the lifetime of the device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ASoC sti driver allocates regmap_field objects during player initialization but never frees them, causing resource leaks when the driver is removed. The fix involves switching from regmap_field_alloc() to devm_regmap_field_alloc() for automatic lifetime management.

MitigationReplace manual regmap_field_alloc() calls with devm_regmap_field_alloc() to ensure proper cleanup when the driver or device is removed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.3, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify kernel version
    Run 'uname -r' or check /proc/version to obtain the running kernel version
    Affected if The kernel version falls within one of the affected ranges: >= 4.3, < 5.10.258; >= 5.11, < 5.15.209; >= 5.16, < 6.1.175; >= 6.2, < 6.6.141; >= 6.7, < 6.12.91; >= 6.13, < 6.18.33; >= 6.19, < 7.0.10
  2. Determine if STI audio driver is present
    Check for the presence of the sti audio driver module or built-in driver in the kernel configuration or loaded modules
    Affected if The sti audio driver (ASoC STI driver) is present in the kernel build
  3. Verify driver initialization occurred
    Check system logs or driver state for evidence that the sti audio driver was initialized and created regmap_field allocations
    Affected if The sti audio driver was loaded and initialized, creating the leaked regmap_field objects
  4. Check for driver removal
    If the driver can be unloaded (rmmod), attempt to unload it and observe if resource cleanup was incomplete
    Affected if The driver has been loaded and unloaded multiple times without proper resource cleanup (the resource leak manifests over time)

A system is affected if it runs a kernel version within the affected ranges AND uses the STI audio driver, particularly if the driver has been loaded/unloaded multiple times causing resource accumulation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.258 / 5.15.209 / 6.1.175 or later
Fixed in 5.10.2585.15.2096.1.175
Interim mitigation

Replace manual regmap_field_alloc() calls with devm_regmap_field_alloc() to ensure proper cleanup when the driver or device is removed.

Recommended fix High confidence

Linux Kernel 5.10.258 / 5.15.209 / 6.1.175 / 6.6.141 (or later, choose based on your current branch)

  1. Identify the currently running Linux kernel version using 'uname -r'
  2. Determine which kernel branch your current version belongs to (e.g., 5.10.x, 5.15.x, 6.1.x, 6.6.x)
  3. Upgrade to a kernel version that includes the fix: for 5.10.x series upgrade to >= 5.10.258, for 5.11-5.15.x series upgrade to >= 5.15.209, for 5.16-6.1.x series upgrade to >= 6.1.175, or for 6.2-6.6.x series upgrade to >= 6.6.141
  4. Apply the kernel upgrade through your distribution's package manager or by compiling from source
  5. Reboot the system to load the fixed kernel
  6. Verify the fix is applied by checking the kernel version and confirming the sti audio driver loads correctly
Caveat Kernel upgrades may require rebuilding third-party kernel modules; ensure compatibility of proprietary drivers with the new kernel version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53065 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data