LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22084: w1: fix NULL pointer dereference in probe

In the Linux kernel, the following vulnerability has been resolved: w1: fix NULL pointer dereference in probe The w1_uart_probe() function calls w1_uart_serdev_open() (which includes devm_serdev_device_open()) before setting the client ops via serdev_device_set_client_ops(). This ordering can trigger a NULL pointer dereference in the serdev controller's receive_buf handler, as it assumes serdev->ops is valid when SERPORT_ACTIVE is set. This is similar to the issue fixed in commit 5e700b384ec1 ("platform/chrome: cros_ec_uart: properly fix race condition") where devm_serdev_device_open() was called before fully initializing the device. Fix the race by ensuring client ops are set before enabling the port via w1_uart_serdev_open().

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 can crash part of the kernel during setup of a 1-Wire UART device. The bug is an initialization race: the port can be enabled before required callbacks are registered. The public sources do not provide CVSS, exploitation evidence, or business-impact details beyond the resolved kernel defect.

Executive priority

Treat as a kernel reliability risk with unclear severity. Patch through standard kernel maintenance, escalating priority for embedded, industrial, or hardware-integrated systems that depend on 1-Wire UART support.

Technical view

w1_uart_probe() called w1_uart_serdev_open(), including devm_serdev_device_open(), before serdev_device_set_client_ops(). If receive_buf runs while SERPORT_ACTIVE is set and serdev->ops is still NULL, a NULL pointer dereference can occur. The fix sets client ops before enabling the port.

Likely exposure

Exposure appears limited to Linux systems with affected kernel versions and the w1_uart serdev path in use. The bundle lists Linux kernel versions and stable fixes, but does not identify distributions, appliances, or default configurations affected.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the source bundle describes a kernel race and NULL pointer dereference rather than a remote attack path.

Researcher notes

The evidence supports an initialization-order race in the Linux w1_uart probe path. Severity, reachable configurations, and exploitability are not established in the bundle. Avoid assuming broad remote exposure without additional platform-specific evidence.

Mitigation direction

  • Update to a kernel containing the listed stable fixes.
  • Check Linux vendor or distribution advisories for packaged kernel availability.
  • Prioritize systems using 1-Wire UART or serdev-connected hardware.
  • If patching is delayed, review vendor guidance for safe configuration workarounds.

Validation and detection

  • Inventory Linux kernel versions across affected asset classes.
  • Identify systems using w1_uart or related serdev hardware paths.
  • Confirm installed kernels include one of the referenced stable commits.
  • Review boot or kernel logs for probe-time NULL dereference symptoms.
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-22084 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
LinuxLinuxa3c08804364e80328a9ffdac59bb26676b938195, a3c08804364e80328a9ffdac59bb26676b938195, a3c08804364e80328a9ffdac59bb26676b938195, a3c08804364e80328a9ffdac59bb26676b938195unaffected
LinuxLinux6.9, 0, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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