NVD / CVE Program· CNA Linux

CVE-2024-38610: drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map()

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb, 3d6586008f7b638f91f3332602592caa8b00b559, 4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4.

Low priority for now. Upgrade to Linux Linux 2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb, 3d6586008f7b638f91f3332602592caa8b00b559, 4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map() Patch series "mm: follow_pte() improvements and acrn follow_pte() fixes". Patch #1 fixes a bunch of issues I spotted in the acrn driver. It compiles, that's all I know. I'll appreciate some review and testing from acrn folks. Patch #2+#3 improve follow_pte(), passing a VMA instead of the MM, adding more sanity checks, and improving the documentation. Gave it a quick test on x86-64 using VM_PAT that ends up using follow_pte(). This patch (of 3): We currently miss handling various cases, resulting in a dangerous follow_pte() (previously follow_pfn()) usage. (1) We're not checking PTE write permissions. Maybe we should simply always require pte_write() like we do for pin_user_pages_fast(FOLL_WRITE)? Hard to tell, so let's check for ACRN_MEM_ACCESS_WRITE for now. (2) We're not rejecting refcounted pages. As we are not using MMU notifiers, messing with refcounted pages is dangerous and can result in use-after-free. Let's make sure to reject them. (3) We are only looking at the first PTE of a bigger range. We only lookup a single PTE, but memmap->len may span a larger area. Let's loop over all involved PTEs and make sure the PFN range is actually contiguous. Reject everything else: it couldn't have worked either way, and rather made use access PFNs we shouldn't be accessing.

Memory safety

BDU:2024-11544

Published: Jun 19, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 11th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 149d5fb7e0124c3763e92edd1fde19417f4d2d09, 02098ac42b7ff055ec72cd083ee1eb0a23481a19, 5.18affected
- b9c43aa0b18da5619aac347d54cb67fe30d1f884 and later · before 5c6705aa47b5b78d7ad36fea832bb69caa5bf49aaffected · git
- 8a6e85f75a83d16a71077e41f2720c691f432002 and later · before afeb0e69627695f759fc73c39c1640dbf8649b32affected · git
- 8a6e85f75a83d16a71077e41f2720c691f432002 and later · before e873f36ec890bece26ecce850e969917bceebbb6affected · git
- 8a6e85f75a83d16a71077e41f2720c691f432002 and later · before 4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4affected · git
- 8a6e85f75a83d16a71077e41f2720c691f432002 and later · before 2c8d6e24930b8ef7d4a81787627c559ae0e0d3bbaffected · git
- 8a6e85f75a83d16a71077e41f2720c691f432002 and later · before 3d6586008f7b638f91f3332602592caa8b00b559affected · git
- 5.15.33 and later · before 5.15.161affected · semver
- 5.16.19 and later · before 5.17affected · semver
- 5.17.2 and later · before 5.18affected · semver

Affected versions · NVD (6)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.15.33 and later · before 5.15.161
linux linux kernel5.16.19 and later · before 5.17
linux linux kernel5.17.2 and later · before 6.1.93
linux linux kernel6.2 and later · before 6.6.33
linux linux kernel6.7 and later · before 6.8.12
linux linux kernel6.9 and later · before 6.9.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.94-1	6.1.94-1
Debian:13	linux	before 6.8.12-1	6.8.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-38607Jun 19, 2024 · macintosh/via-macii: Fix "BUG: sleeping function called from invalid context"
22Monitor
← EarlierCVE-2024-38609Jun 19, 2024 · wifi: mt76: connac: check for null before dereferencing
22Monitor
Later →CVE-2024-38611Jun 19, 2024 · media: i2c: et8ek8: Don't strip remove function when driver is builtin
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb	Vendor (CNA)
Linux Linux	3d6586008f7b638f91f3332602592caa8b00b559	Vendor (CNA)
Linux Linux	4c4ba3cf3a15ccfbaf787d0296fa42cdb00da9b4	Vendor (CNA)
Linux Linux	5.15.161	Vendor (CNA)
Linux Linux	5.17	Vendor (CNA)
Linux Linux	5.18	Vendor (CNA)
Linux Linux	5c6705aa47b5b78d7ad36fea832bb69caa5bf49a	Vendor (CNA)
Linux Linux	afeb0e69627695f759fc73c39c1640dbf8649b32	Vendor (CNA)
Linux Linux	e873f36ec890bece26ecce850e969917bceebbb6	Vendor (CNA)
debian:linux	6.1.94-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/2c8d6e24930b8ef7d4a81787627c559ae0e0d3bb

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records