# CVE-2024-44949: parisc: fix a possible DMA corruption

> A DMA alignment issue in the Linux kernel parisc architecture can cause data corruption when unrelated allocations share cache lines.

- **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 Sep 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-50254, BELL-CVE-2024-44949, DEBIAN-CVE-2024-44949, GHSA-wxc5-fq68-h9mh, ROOT-OS-DEBIAN-11-CVE-2024-44949, UBUNTU-CVE-2024-44949

## What is CVE-2024-44949?

CVE-2024-44949 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Sep 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:

parisc: fix a possible DMA corruption

ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be
possible that two unrelated 16-byte allocations share a cache line. If
one of these allocations is written using DMA and the other is written
using cached write, the value that was written with DMA may be
corrupted.

This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 -
that's the largest possible cache line size.

As different parisc microarchitectures have different cache line size, we
define arch_slab_minalign(), cache_line_size() and
dma_get_cache_alignment() so that the kernel may tune slab cache
parameters dynamically, based on the detected cache line size.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-44949 being exploited?

There is no known exploitation of CVE-2024-44949 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-44949 and fix it if it is affected.

What it is: CVE-2024-44949 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Sep 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-44949 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-44949/ (Markdown: https://insights.sbomify.com/CVE-2024-44949/index.md)
```

## Sources

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

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