# CVE-2024-47674: mm: avoid leaving partial pfn mappings around in error case

> A use-after-free vulnerability in the Linux kernel's PFN mapping error handling allows attackers to execute arbitrary code or escalate privileges.

- **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:** 15 Oct 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-50582, AZL-50597, BELL-CVE-2024-47674, DEBIAN-CVE-2024-47674, GHSA-qjwp-794r-6x7v, UBUNTU-CVE-2024-47674

## What is CVE-2024-47674?

CVE-2024-47674 is a high-severity use after free vulnerability in Linux kernel, published on 15 Oct 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:

mm: avoid leaving partial pfn mappings around in error case

As Jann points out, PFN mappings are special, because unlike normal
memory mappings, there is no lifetime information associated with the
mapping - it is just a raw mapping of PFNs with no reference counting of
a 'struct page'.

That's all very much intentional, but it does mean that it's easy to
mess up the cleanup in case of errors.  Yes, a failed mmap() will always
eventually clean up any partial mappings, but without any explicit
lifetime in the page table mapping itself, it's very easy to do the
error handling in the wrong order.

In particular, it's easy to mistakenly free the physical backing store
before the page tables are actually cleaned up and (temporarily) have
stale dangling PTE entries.

To make this situation less error-prone, just make sure that any partial
pfn mapping is torn down early, before any other error handling.

Weakness: CWE-459 (Incomplete Cleanup)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-47674 being exploited?

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

What it is: CVE-2024-47674 is a high-severity use after free vulnerability in Linux kernel, published on 15 Oct 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-47674 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-47674/ (Markdown: https://insights.sbomify.com/CVE-2024-47674/index.md)
```

## Sources

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

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