LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38559: platform/x86/intel/pmt: fix a crashlog NULL pointer access

In the Linux kernel, the following vulnerability has been resolved: platform/x86/intel/pmt: fix a crashlog NULL pointer access Usage of the intel_pmt_read() for binary sysfs, requires a pcidev. The current use of the endpoint value is only valid for telemetry endpoint usage. Without the ep, the crashlog usage causes the following NULL pointer exception: BUG: kernel NULL pointer dereference, address: 0000000000000000 Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:intel_pmt_read+0x3b/0x70 [pmt_class] Code: Call Trace: <TASK> ? sysfs_kf_bin_read+0xc0/0xe0 kernfs_fop_read_iter+0xac/0x1a0 vfs_read+0x26d/0x350 ksys_read+0x6b/0xe0 __x64_sys_read+0x1d/0x30 x64_sys_call+0x1bc8/0x1d70 do_syscall_64+0x6d/0x110 Augment struct intel_pmt_entry with a pointer to the pcidev to avoid the NULL pointer exception.

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 crash bug in Intel PMT crashlog handling. Reading a specific binary sysfs crashlog path can hit a NULL pointer and crash kernel code. The provided sources do not include CVSS, impact scoring, privilege requirements, or evidence of exploitation.

Executive priority

Treat as a patch-management item with uncertain severity. Prioritize affected Linux servers where a local kernel crash would affect availability, but do not escalate as exploited without new evidence.

Technical view

The flaw is in platform/x86/intel/pmt. intel_pmt_read() requires a PCI device pointer, but crashlog usage could reach it without the endpoint data used by telemetry. The fix adds a pcidev pointer to intel_pmt_entry to prevent the NULL dereference during sysfs binary reads.

Likely exposure

Exposure appears limited to Linux systems with affected kernel builds and Intel PMT crashlog functionality present. The source bundle lists Linux 6.12 and later stable lines through 6.17 as affected context, but does not provide full distribution mapping.

Exploitation context

No active exploitation is supported by the supplied sources, and KEV is false. The observable failure is a kernel NULL pointer dereference triggered through a sysfs binary read path, suggesting denial-of-service risk rather than data theft based on current evidence.

Researcher notes

The bundle lacks CVSS, CWE, detailed access requirements, and distro-specific affected ranges. Analysis should stay tied to the upstream Linux fix and confirm whether local sysfs permissions make the crash path reachable in each environment.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the referenced stable PMT fixes.
  • Check vendor advisories for exact fixed kernel packages and backports.
  • Restrict unnecessary local access to affected sysfs crashlog interfaces where feasible.
  • Prioritize systems using Intel PMT crashlog features or relevant platform/x86 drivers.

Validation and detection

  • Inventory Linux kernel versions and vendor patch levels across affected fleets.
  • Confirm whether Intel PMT crashlog sysfs entries are present on target systems.
  • Verify installed kernels include one of the referenced stable fix commits or vendor backports.
  • Review kernel logs for NULL pointer dereferences involving intel_pmt_read or pmt_class.
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-2025-38559 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
LinuxLinux045a513040cc0242d364c05c3791594e2294f32d, 045a513040cc0242d364c05c3791594e2294f32d, 045a513040cc0242d364c05c3791594e2294f32d, 045a513040cc0242d364c05c3791594e2294f32dunaffected
LinuxLinux6.12, 0, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

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