CVE-2026-99503 in Linuxinfo

Summary

by MITRE • 11/19/2026

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

ata: sata_fsl: Fix use-after-free of host_priv on probe() failure

sata_fsl_host_stop() releases hcr_base and host_priv:

static void sata_fsl_host_stop(struct ata_host *host) {
struct sata_fsl_host_priv *host_priv = host->private_data;

iounmap(host_priv->hcr_base); kfree(host_priv); }

->host_stop() is called by the driver core through the ata_host_stop() devres action which ata_host_start() registers, so it is called both when the device is unbound and when probe() fails after the host has been started.

The error_exit_with_cleanup label of sata_fsl_probe() releases hcr_base and host_priv as well, and it is reachable from the two device_create_file() calls which are done after the host has been activated. In that case sata_fsl_host_stop() runs on an already freed host_priv, resulting in a use-after-free and a double iounmap()/kfree().

Add a separate error label for the failures happening after the host has been activated, which only detaches the host and leaves hcr_base and host_priv to sata_fsl_host_stop().

Note that ata_host_detach() is dropped from error_exit_with_cleanup, as that label is now only reachable while host is still NULL.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The Linux kernel driver for Freescale SATA controllers contains a critical memory management flaw within its probe function implementation. This vulnerability manifests as a use-after-free condition coupled with double free and double unmapping errors during the device initialization phase. The root cause lies in an incorrect handling of error paths when the hardware has already been partially activated but subsequent setup steps fail. Specifically, the driver registers a cleanup action via devres that invokes sata_fsl_host_stop upon unbinding or probe failure after activation. This function is responsible for releasing resources such as hcr_base and host_priv. However, if device_create_file calls succeed while later initialization steps fail, control flow jumps to an error label that independently frees these same resources before the driver core triggers the registered stop routine. Consequently, sata_fsl_host_stop attempts to free memory that has already been deallocated by the probe failure path, leading to undefined behavior and potential system instability or kernel panic.

From a technical perspective, this flaw represents a classic race condition in resource lifecycle management within asynchronous initialization sequences. The driver fails to distinguish between early-stage failures where resources have not yet been committed to hardware operation and late-stage failures where the host controller is already active and managed by the device core's devres framework. When probe() proceeds past ata_host_start(), it registers sata_fsl_host_stop as a cleanup action. Any subsequent failure that triggers error_exit_with_cleanup results in manual invocation of iounmap and kfree on host_priv. Since the driver core will subsequently call sata_fsl_host_stop due to the registered devres action, these resources are freed twice. This violates fundamental memory safety principles where each allocation must have exactly one corresponding deallocation point that is mutually exclusive with other deallocation paths for the same resource instance.

The operational impact of this vulnerability includes kernel crashes, particularly in environments where SATA devices are frequently plugged and unplugged or when drivers fail to initialize due to hardware incompatibility or configuration errors. An attacker who can trigger probe failures repeatedly may exploit this instability to cause denial-of-service conditions by exhausting system resources through repeated allocation-deallocation cycles that corrupt the slab allocator metadata. While direct code execution is unlikely given the nature of double-free in kernel space without additional primitives, memory corruption could potentially be leveraged for privilege escalation if adjacent heap structures are manipulated effectively. The vulnerability affects systems relying on Freescale/NXP PowerPC or similar architectures utilizing this specific SATA controller driver, impacting enterprise storage subsystems and embedded devices dependent on reliable block device initialization.

This issue aligns with CWE-416: Use After Free, as the code accesses memory after it has been freed by a different execution path. It also relates to CWE-772: Missing Release of Resource after Effective Lifetime if viewed from the perspective that resources are not properly tracked across state transitions, although the primary issue is double release rather than missing release. In terms of MITRE ATT&CK mapping, this falls under T1499: Endpoint Denial of Service, as successful exploitation leads to system instability or crash. It may also be categorized under T1055: Process Injection if an attacker could leverage the memory corruption for further payload delivery, though the primary classification remains resource management error leading to denial of service.

Mitigation strategies involve applying kernel patches that restructure the probe function's error handling logic. The fix requires separating early-stage cleanup from late-stage teardown operations. Specifically, when failures occur after ata_host_start has been called and registered its devres action, the driver should only detach the host using ata_host_detach without manually freeing hcr_base or host_priv. This ensures that sata_fsl_host_stop remains the sole entity responsible for releasing these resources via the standard device unbinding path. Developers must ensure strict separation between pre-activation error paths and post-activation cleanup routines to prevent overlapping resource deallocation. System administrators should apply updated kernel packages containing this fix immediately, particularly on systems using affected Freescale SATA controllers, to maintain stability during hardware enumeration failures or driver load errors.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00174

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!