LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53684: xfrm: Zero padding when dumping algos and encap

In the Linux kernel, the following vulnerability has been resolved: xfrm: Zero padding when dumping algos and encap When copying data to user-space we should ensure that only valid data is copied over. Padding in structures may be filled with random (possibly sensitve) data and should never be given directly to user-space. This patch fixes the copying of xfrm algorithms and the encap template in xfrm_user so that padding is zeroed.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53684 is a Linux kernel information disclosure issue. When the kernel reports certain XFRM algorithm and encapsulation data to user space, unused structure padding could include random, possibly sensitive kernel data. The fix zeros that padding before copying. Public sources do not report active exploitation or a CVSS score.

Executive priority

Treat as a routine-to-moderate Linux kernel update priority. The impact is potential information disclosure, not confirmed remote code execution. Increase urgency for shared, multi-user, or sensitive workloads once vendor advisories confirm exposure.

Technical view

The resolved Linux kernel bug is in xfrm_user dumping of algorithms and encap templates. Structure padding was not cleared before data was copied to user space, potentially exposing uninitialized or sensitive bytes. Referenced stable commits implement zeroing of padding. The provided affected-version data is limited and should be validated against distribution kernels.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds with the relevant XFRM code present. The source bundle lists affected Linux version entries including 5.11, 5.15.106, 6.1.23, 6.2.10, and 6.3, but does not provide clear distribution-specific package ranges.

Exploitation context

The issue concerns kernel-to-user-space data disclosure. Sources do not provide prerequisites, required privileges, exploit availability, or evidence of active exploitation. It is not listed as CISA KEV in the provided data.

Researcher notes

The public record lacks CVSS, CWE, exploit status, and precise version-range semantics. Analysis should focus on confirming backports of the zero-padding fixes and determining whether local user-space access to affected XFRM dump paths is possible in target environments.

Mitigation direction

  • Apply distribution kernel updates that include the referenced Linux stable fixes.
  • If building kernels, include the relevant upstream stable commits.
  • Track Linux and distribution advisories for clarified affected ranges.
  • Prioritize shared or multi-user Linux systems for review.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Compare installed kernels with vendor advisories and CVE affected entries.
  • Confirm kernel packages include one of the referenced stable commits.
  • Review whether XFRM functionality is enabled on in-scope systems.
Prepared
Confidence
medium
Sources
6

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-53684 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
5Source 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
LinuxLinuxc7a5899eb26e2a4d516d53f65b6dd67be2228041, c7a5899eb26e2a4d516d53f65b6dd67be2228041, c7a5899eb26e2a4d516d53f65b6dd67be2228041, c7a5899eb26e2a4d516d53f65b6dd67be2228041unaffected
LinuxLinux5.11, 0, 5.15.106, 6.1.23, 6.2.10, 6.3affected
Weakness

CWE details

No CWE listed

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