LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54307: ptp_qoriq: fix memory leak in probe()

In the Linux kernel, the following vulnerability has been resolved: ptp_qoriq: fix memory leak in probe() Smatch complains that: drivers/ptp/ptp_qoriq.c ptp_qoriq_probe() warn: 'base' from ioremap() not released. Fix this by revising the parameter from 'ptp_qoriq->base' to 'base'. This is only a bug if ptp_qoriq_init() returns on the first -ENODEV error path. For other error paths ptp_qoriq->base and base are the same. And this change makes the code more readable.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-54307 is a Linux kernel bug in the ptp_qoriq driver where mapped memory may not be released during a specific probe failure path. The source describes a memory leak, not remote code execution or privilege escalation. Business urgency is mainly for systems using affected Linux kernels with this driver or related QorIQ PTP hardware.

Executive priority

Treat this as routine kernel hygiene unless your environment depends on QorIQ PTP hardware or custom kernels. There is no cited active exploitation or high-impact severity data in the bundle, but affected kernel fleets should still receive normal vendor-supported updates.

Technical view

The issue is in drivers/ptp/ptp_qoriq.c during ptp_qoriq_probe(). Smatch reported that base from ioremap() was not released. The fix changes cleanup handling so the mapped base is released on the first -ENODEV path from ptp_qoriq_init(). Kernel stable commits are referenced as fixes.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the ptp_qoriq driver is present and its probe path is exercised. Systems without this driver or relevant hardware are less likely to be exposed, but package configuration should be verified.

Exploitation context

The bundle does not cite active exploitation, public exploit use, KEV listing, CVSS, or a practical attack path. The described impact is a memory leak on a driver initialization error path, so exploitation evidence is currently incomplete.

Researcher notes

The key condition is narrow: ptp_qoriq_init() returning on the first -ENODEV path left the ioremap() base unreleased. The CVE data lacks CVSS, CWE, and exploitability detail, so validation should focus on code lineage, driver configuration, hardware presence, and backported fixes.

Mitigation direction

  • Check Linux vendor advisories for the affected kernel package.
  • Update to a kernel containing the referenced stable fix commits.
  • Prioritize systems using QorIQ PTP or the ptp_qoriq driver.
  • Use normal kernel change controls and reboot requirements.
  • Track distribution backports rather than only upstream version numbers.

Validation and detection

  • Inventory Linux kernels and enabled ptp_qoriq driver usage.
  • Review kernel package changelogs for CVE-2023-54307 or referenced commits.
  • Confirm whether relevant hardware can trigger the probe path.
  • Verify patched systems after reboot with running kernel version checks.
  • Document exceptions for systems without the driver or hardware path.
Prepared
Confidence
medium
Sources
8

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-54307 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
7Source 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
LinuxLinux7f4399ba405b6201fb318b43091703a34b1489ab, 7f4399ba405b6201fb318b43091703a34b1489ab, 7f4399ba405b6201fb318b43091703a34b1489ab, 7f4399ba405b6201fb318b43091703a34b1489ab, 7f4399ba405b6201fb318b43091703a34b1489ab, 7f4399ba405b6201fb318b43091703a34b1489abunaffected
LinuxLinux5.2, 0, 5.4.240, 5.10.177, 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.