LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23065: platform/x86/amd: Fix memory leak in wbrf_record()

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd: Fix memory leak in wbrf_record() The tmp buffer is allocated using kcalloc() but is not freed if acpi_evaluate_dsm() fails. This causes a memory leak in the error path. Fix this by explicitly freeing the tmp buffer in the error handling path of acpi_evaluate_dsm().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in an AMD platform driver error path. If a specific ACPI DSM call fails, allocated memory is not released. The public sources do not provide a CVSS score, real-world exploitation evidence, or a named workaround.

Executive priority

Treat as a routine kernel maintenance item unless exposed fleet analysis shows broad affected AMD Linux coverage. There is no cited exploitation or severity score, but kernel memory leaks can become reliability concerns if triggerable.

Technical view

In platform/x86/amd, wbrf_record() allocates a tmp buffer with kcalloc(). When acpi_evaluate_dsm() fails, the error path previously returned without freeing tmp. Stable kernel commits fix the leak by freeing the buffer in that failure path.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream kernels containing the vulnerable platform/x86/amd code. The bundle lists Linux kernel versions including 6.8, 6.12.68, 6.18.8, and 6.19, but downstream distro backport status must be verified.

Exploitation context

The bundle does not cite active exploitation, proof-of-concept activity, or KEV listing. Impact appears tied to repeated triggering of a driver error path, but the sources do not establish attacker reachability or practical exploit conditions.

Researcher notes

Key uncertainty is triggerability. The source confirms a missing kfree-style cleanup after acpi_evaluate_dsm() failure, but not whether unprivileged users can induce repeated failures. Review downstream patches and platform context before assigning operational risk.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • Use distribution vendor advisories to confirm patched package versions.
  • If updates are pending, follow vendor guidance; no workaround is named in the bundle.
  • Prioritize systems using affected AMD platform kernel paths.

Validation and detection

  • Inventory Linux kernel versions across affected server and endpoint fleets.
  • Check package changelogs for CVE-2026-23065 or referenced stable commits.
  • Confirm downstream kernels include the wbrf_record() error-path free fix.
  • Monitor vendor advisories for clarified affected-version mapping and severity.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23065 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux58e82a62669da52e688f4a8b89922c1839bf1001, 58e82a62669da52e688f4a8b89922c1839bf1001, 58e82a62669da52e688f4a8b89922c1839bf1001unaffected
LinuxLinux6.8, 0, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.