LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53181: dma-buf/dma-resv: Stop leaking on krealloc() failure

In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-resv: Stop leaking on krealloc() failure Currently dma_resv_get_fences() will leak the previously allocated array if the fence iteration got restarted and the krealloc_array() fails. Free the old array by hand, and make sure we still clear the returned *fences so the caller won't end up accessing freed memory. Some (but not all) of the callers of dma_resv_get_fences() seem to still trawl through the array even when dma_resv_get_fences() failed. And let's zero out *num_fences as well for good measure.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory-management bug in dma-buf reservation fence handling. Under allocation failure during a restarted fence iteration, the kernel could leak a previously allocated array. Public sources do not provide CVSS, exploitation evidence, or distribution-specific impact.

Executive priority

Treat as a kernel maintenance item with uncertain severity. It deserves inclusion in normal patch cycles, with higher priority where untrusted local workloads share Linux hosts using graphics or DMA-BUF-related functionality.

Technical view

CVE-2023-53181 affects Linux kernel dma-buf/dma-resv code. dma_resv_get_fences() could leak an old fences array when krealloc_array() failed after iteration restart. The referenced fix frees the prior array and clears returned fence count/pointer state to reduce unsafe caller behavior after failure.

Likely exposure

Exposure is limited to Linux kernels containing the affected dma-buf/dma-resv implementation before the referenced stable fixes. The bundle does not identify affected distributions, packages, appliances, or whether remote attack surfaces exist.

Exploitation context

The source bundle says this is not in KEV and provides no evidence of active exploitation, public exploit code, or weaponization. Triggerability depends on kernel code paths reaching dma_resv_get_fences() and allocation-failure behavior.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or distro mapping is provided. The core issue is allocation-failure cleanup in dma_resv_get_fences(), not a documented remote vector. Validate impact against the exact kernel tree and vendor backports.

Mitigation direction

  • Apply Linux kernel vendor updates that include the referenced dma-buf/dma-resv fixes.
  • Check distribution advisories for backported patches and exact fixed package versions.
  • Prioritize systems with untrusted local workloads using graphics, GPU, or DMA-BUF paths.
  • If no vendor package exists, track the referenced stable commits for kernel maintenance decisions.

Validation and detection

  • Inventory Linux kernel versions and distribution package revisions across affected assets.
  • Confirm whether vendor advisories map installed kernels to the referenced fixes.
  • Review kernel changelogs for the dma-buf/dma-resv krealloc failure fix.
  • Monitor security advisories for CVSS, exploitability notes, or distro-specific affected ranges.
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-2023-53181 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
LinuxLinuxd3c80698c9f58a0683badf78793eebaa0c71afbd, d3c80698c9f58a0683badf78793eebaa0c71afbd, d3c80698c9f58a0683badf78793eebaa0c71afbdunaffected
LinuxLinux5.16, 0, 6.1.42, 6.4.7, 6.5affected
Weakness

CWE details

No CWE listed

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