Skip to main content
Menu
CVEs

Linux kernel use-after-free in sata_fsl SATA driver on probe failure

CVE-2026-99503Published November 19, 2026, updated

Exploited
No known exploitation
Fix
Fixed in 4.5, 4.10, 4.15, 4.20, 5.5, and 2 more
Who is exposed
Not reported

Summary

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.

What to do

Upgrade to a fixed version: 4.5, 4.10, 4.15, 4.20, 5.5, or one of 2 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99503 (ata: sata_fsl: Fix use-after-free of host_priv on probe() failure), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99503 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 4.4.294, fixed in 4.5; from 4.9.292, fixed in 4.10; from 4.14.257, fixed in 4.15; from 4.19.220, fixed in 4.20; from 5.4.164, fixed in 5.5; from 5.10.84, fixed in 5.11; from 5.15.7, fixed in 5.16
- Linux Linux: versions 5.16
Fixed versions: 4.5, 4.10, 4.15, 4.20, 5.5, 5.11, 5.16.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99503 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99503 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/3e00737e95485b2a35bf5f515f56a4c416d5971f
- https://git.kernel.org/stable/c/59eac6863eede5957bfd8872633608431ac42d3c
- https://git.kernel.org/stable/c/9d9d62dfef3609f664c60f6fe61528a2e876a64b
- https://git.kernel.org/stable/c/70b1196740d61aabda13b2ad0e9c1dfa2ef9cfa3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99503
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99503"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 6

Questions about CVE-2026-99503

Is CVE-2026-99503 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-99503?

Linux: from 4.4.294 before 4.5; from 4.9.292 before 4.10; from 4.14.257 before 4.15; from 4.19.220 before 4.20; from 5.4.164 before 5.5; from 5.10.84 before 5.11; from 5.15.7 before 5.16. Linux: version 5.16.

Source: cve.now feed data

How do I fix CVE-2026-99503?

Upgrade to a fixed version: 4.5, 4.10, 4.15, 4.20, 5.5, or one of 2 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.