Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-57945: riscv: mm: Fix the out of bound issue of vmemmap address

Noroxi assessment

Priority: Monitor (action score 28/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 04350304428063da6a55a8a4597d409dc69148b2, 5.10.258, 5.16.

Low priority for now. Upgrade to Linux Linux 04350304428063da6a55a8a4597d409dc69148b2, 5.10.258, 5.16 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: riscv: mm: Fix the out of bound issue of vmemmap address In sparse vmemmap model, the virtual address of vmemmap is calculated as: ((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)). And the struct page's va can be calculated with an offset: (vmemmap + (pfn)). However, when initializing struct pages, kernel actually starts from the first page from the same section that phys_ram_base belongs to. If the first page's physical address is not (phys_ram_base >> PAGE_SHIFT), then we get an va below VMEMMAP_START when calculating va for it's struct page. For example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the first page in the same section is actually pfn 0x80000. During init_unavailable_range(), we will initialize struct page for pfn 0x80000 with virtual address ((struct page *)VMEMMAP_START - 0x2000), which is below VMEMMAP_START as well as PCI_IO_END. This commit fixes this bug by introducing a new variable 'vmemmap_start_pfn' which is aligned with memory section size and using it to calculate vmemmap address instead of phys_ram_base.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jan 21, 2025
Updated
Aug 5, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
7.1
CNA · Linux
7.8
0.7 point gap

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

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.

Follow CVE-2024-57945

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel5.10.212 and later · before 5.11
  • linux linux kernel5.15.151 and later · before 5.16
  • linux linux kernel6.1.81 and later · before 6.1.140
  • linux linux kernel6.6.21 and later · before 6.6.72
  • linux linux kernel6.7.9 and later · before 6.8
  • linux linux kernel6.8.1 and later · before 6.12.10
  • linux linux kernel6.13
  • linux linux kernel6.8

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

    • 5941a90c55d3bfba732b32208d58d997600b44ef, 2a1728c15ec4f45ed9248ae22f626541c179bfbe, 6.8affected
    • 8af1c121b0102041809bc137ec600d1865eaeedd and later · before 04350304428063da6a55a8a4597d409dc69148b2affected · git
    • 8310080799b40fd9f2a8b808c657269678c149af and later · before 92f08673d3f1893191323572f60e3c62f2e57c2faffected · git
    • a278d5c60f21aa15d540abb2f2da6e6d795c3e6e and later · before a4a7ac3d266008018f05fae53060fcb331151a14affected · git
    • a11dd49dcb9376776193e15641f84fcc1e5980c9 and later · before d2bd51954ac8377c2f1eb1813e694788998add66affected · git
    • a11dd49dcb9376776193e15641f84fcc1e5980c9 and later · before f754f27e98f88428aaf6be6e00f5cbce97f62d4baffected · git
    • 5.10.212 and later · before 5.10.258affected · semver
    • 6.1.81 and later · before 6.1.140affected · semver
    • 6.6.21 and later · before 6.6.72affected · semver
    • 5.15.151 and later · before 5.16affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.140-1~deb11u16.1.140-1~deb11u1
Debian:12linuxbefore 6.1.140-16.1.140-1
Debian:13linuxbefore 6.12.10-16.12.10-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-57943Jan 21, 2025 · exfat: fix the new buffer was not zeroed before writing
    31Monitor
  • ← EarlierCVE-2024-57944Jan 21, 2025 · iio: adc: ti-ads1298: Add NULL check in ads1298_init
    22Monitor
  • Later →CVE-2024-57946Jan 21, 2025 · virtio-blk: don't keep queue frozen during system suspend
    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 / packageFixed versionSource
Linux Linux04350304428063da6a55a8a4597d409dc69148b2Vendor (CNA)
Linux Linux5.10.258Vendor (CNA)
Linux Linux5.16Vendor (CNA)
Linux Linux6.1.140Vendor (CNA)
Linux Linux6.6.72Vendor (CNA)
Linux Linux6.8Vendor (CNA)
Linux Linux92f08673d3f1893191323572f60e3c62f2e57c2fVendor (CNA)
Linux Linuxa4a7ac3d266008018f05fae53060fcb331151a14Vendor (CNA)
Linux Linuxd2bd51954ac8377c2f1eb1813e694788998add66Vendor (CNA)
Linux Linuxf754f27e98f88428aaf6be6e00f5cbce97f62d4bVendor (CNA)
debian:linux6.1.140-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.140-1~deb11u1 · Debian:11Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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
none
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
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

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

nvd-primary

Attack context

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

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (5 more)

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

All records