# CVE-2024-53127: Revert "mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K"

> A regression in the Linux kernel MMC driver causes system panics and data corruption when booting from SD cards on specific hardware.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Dec 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-54120, BELL-CVE-2024-53127, DEBIAN-CVE-2024-53127, GHSA-5cwm-fg2p-g6pp, UBUNTU-CVE-2024-53127

## What is CVE-2024-53127?

CVE-2024-53127 is a high-severity denial of service vulnerability in Linux kernel, published on 4 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Revert "mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K"

The commit 8396c793ffdf ("mmc: dw_mmc: Fix IDMAC operation with pages
bigger than 4K") increased the max_req_size, even for 4K pages, causing
various issues:
- Panic booting the kernel/rootfs from an SD card on Rockchip RK3566
- Panic booting the kernel/rootfs from an SD card on StarFive JH7100
- "swiotlb buffer is full" and data corruption on StarFive JH7110

At this stage no fix have been found, so it's probably better to just
revert the change.

This reverts commit 8396c793ffdf28bb8aee7cfe0891080f8cab7890.

## Which versions are affected by CVE-2024-53127?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-53127?

Apply the vendor's patch.

## Is CVE-2024-53127 being exploited?

There is no known exploitation of CVE-2024-53127 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53127 and fix it if it is affected.

What it is: CVE-2024-53127 is a high-severity denial of service vulnerability in Linux kernel, published on 4 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53127 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53127/ (Markdown: https://insights.sbomify.com/CVE-2024-53127/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53127
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53127
- OSV: https://osv.dev/vulnerability/CVE-2024-53127

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53127/
Summaries are generated and may contain mistakes; the official description above is the record.