Skip to main content

Linux Kernel CVE-2026-64230

| EUVDEUVD-2026-48638 MEDIUM
NULL Pointer Dereference (CWE-476)
2026-07-24 Linux GHSA-9pch-737p-3qc4
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Hardware-specific local access required (AV:L), low privilege sufficient to be present on system when IRQ fires (PR:L), impact limited to kernel availability crash with no confidentiality or integrity exposure.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 12, 2026 - 19:25 vuln.today
CVSS changed
Aug 12, 2026 - 19:22 NVD
5.5 (MEDIUM)
Patch available
Jul 24, 2026 - 17:48 EUVD
CVE Published
Jul 24, 2026 - 15:23 nvd
MEDIUM 5.5
CVE Published
Jul 24, 2026 - 15:23 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

regulator: tps65219: fix irq_data.rdev not being assigned

Commit 64a6b577490c ("regulator: tps65219: Remove debugging helper function") removed the tps65219_get_rdev_by_name() helper along with the irq_data.rdev assignment that depended on it. This left irq_data.rdev uninitialized for all IRQs, causing undefined behavior when regulator_notifier_call_chain() is called from the IRQ handler:

Internal error: Oops: 0000000096000004 pc : regulator_notifier_call_chain lr : tps65219_regulator_irq_handler Call trace: regulator_notifier_call_chain tps65219_regulator_irq_handler handle_nested_irq regmap_irq_thread irq_thread_fn irq_thread kthread ret_from_fork

Instead of restoring a dedicated lookup array, restructure the probe function to combine regulator registration with IRQ registration in the same loop. This way the rdev returned by devm_regulator_register() is naturally available for assigning to irq_data.rdev without any auxiliary data structure.

Non-regulator IRQs (SENSOR, TIMEOUT) that don't correspond to any registered regulator are registered with rdev=NULL, and the IRQ handler is protected with a NULL check to avoid crashing.

AnalysisAI

Kernel panic via NULL pointer dereference in the Linux tps65219 PMIC regulator driver crashes affected systems when a hardware IRQ fires on the device, producing a local denial-of-service condition. The regression was introduced by commit 64a6b577490c, which removed the helper function tps65219_get_rdev_by_name() and inadvertently eliminated the only code path that assigned irq_data.rdev, leaving the pointer uninitialized for every registered IRQ. Systems running Linux kernel versions from that commit through the stable-branch fix points (6.18.34 and 7.0.11) on hardware equipped with the TI tps65219 PMIC are affected; no public exploit has been identified and the EPSS score of 0.17% reflects low exploitation probability.

Technical ContextAI

The tps65219 is a Texas Instruments multi-rail power management IC (PMIC) integrated in select embedded Linux boards. The Linux kernel's regulator subsystem manages voltage rails through a dedicated driver (drivers/regulator/tps65219-regulator.c) that registers IRQ handlers for hardware fault events such as overcurrent and undervoltage. Commit 64a6b577490c removed the lookup helper tps65219_get_rdev_by_name() along with the only assignment of irq_data.rdev - a struct regulator_dev * pointer used by the IRQ handler to identify which regulator raised the event. After the regression, every IRQ entry carries an uninitialized (effectively NULL on zero-initialized allocations) rdev pointer. When a hardware interrupt fires, the handler calls regulator_notifier_call_chain() with this NULL pointer, triggering a kernel Oops (Internal error: 0000000096000004 on ARM64). CWE-476 (NULL Pointer Dereference) accurately classifies the root cause. The CPE string cpe:2.3:a:linux:linux:* confirms the affected software is the mainline Linux kernel.

RemediationAI

The upstream fix is confirmed in three stable-branch commits: 6827647fd2dcf4e7f355478a42e82f51e0b5344c (https://git.kernel.org/stable/c/6827647fd2dcf4e7f355478a42e82f51e0b5344c), b986f88b22a5374191c195c073350bbeb1bb6518 (https://git.kernel.org/stable/c/b986f88b22a5374191c195c073350bbeb1bb6518), and f9b2d3b703d13df50c630997dfdc25648e96db0d (https://git.kernel.org/stable/c/f9b2d3b703d13df50c630997dfdc25648e96db0d). Operators should upgrade to Linux 6.18.34, 7.0.11, or 7.1 or later; Ubuntu users should apply USN-8618-1 via standard package updates. For systems where immediate kernel updates are not possible and the tps65219 hardware is not operationally required, blacklisting the tps65219-regulator module prevents the IRQ handler from registering and eliminates the crash path - however, this disables all power management functions for tps65219-connected voltage rails and may cause hardware instability on boards that depend on the PMIC for core rail control.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-64230 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy