Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26947: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses

Noroxi assessment

Priority: Monitor (action score 22/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.23% (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 0c027c2bad7f5111c51a358b5d392e1a695dabff, 0c66c6f4e21cb22220cbd8821c5c73fc157d20dc, 5.11; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.

Low priority for now. Upgrade to Linux Linux 0c027c2bad7f5111c51a358b5d392e1a695dabff, 0c66c6f4e21cb22220cbd8821c5c73fc157d20dc, 5.11; azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1 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: ARM: 9359/1: flush: check if the folio is reserved for no-mapping addresses Since commit a4d5613c4dc6 ("arm: extend pfn_valid to take into account freed memory map alignment") changes the semantics of pfn_valid() to check presence of the memory map for a PFN. A valid page for an address which is reserved but not mapped by the kernel[1], the system crashed during some uio test with the following memory layout: node 0: [mem 0x00000000c0a00000-0x00000000cc8fffff] node 0: [mem 0x00000000d0000000-0x00000000da1fffff] the uio layout is:0xc0900000, 0x100000 the crash backtrace like: Unable to handle kernel paging request at virtual address bff00000 [...] CPU: 1 PID: 465 Comm: startapp.bin Tainted: G O 5.10.0 #1 Hardware name: Generic DT based system PC is at b15_flush_kern_dcache_area+0x24/0x3c LR is at __sync_icache_dcache+0x6c/0x98 [...] (b15_flush_kern_dcache_area) from (__sync_icache_dcache+0x6c/0x98) (__sync_icache_dcache) from (set_pte_at+0x28/0x54) (set_pte_at) from (remap_pfn_range+0x1a0/0x274) (remap_pfn_range) from (uio_mmap+0x184/0x1b8 [uio]) (uio_mmap [uio]) from (__mmap_region+0x264/0x5f4) (__mmap_region) from (__do_mmap_mm+0x3ec/0x440) (__do_mmap_mm) from (do_mmap+0x50/0x58) (do_mmap) from (vm_mmap_pgoff+0xfc/0x188) (vm_mmap_pgoff) from (ksys_mmap_pgoff+0xac/0xc4) (ksys_mmap_pgoff) from (ret_fast_syscall+0x0/0x5c) Code: e0801001 e2423001 e1c00003 f57ff04f (ee070f3e) ---[ end trace 09cf0734c3805d52 ]--- Kernel panic - not syncing: Fatal exception So check if PG_reserved was set to solve this issue. [1]: https://lore.kernel.org/lkml/Zbtdue57RO0QScJM@linux.ibm.com/

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 1, 2024
Updated
Oct 30, 2026
EPSS
0.2% · 13th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 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.

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-26947

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.

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.4.167 and later · before 5.5
  • linux linux kernel5.10.87 and later · before 5.11
  • linux linux kernel5.14 and later · before 6.6.24
  • linux linux kernel6.7 and later · before 6.7.12
  • linux linux kernel6.8 and later · before 6.8.3

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

    • 6026d4032dbbe3d7f4ac2c8daa923fe74dcf41c4, 65c578935bcc26ddc04e6757b2c7be95bf235b31, 5.14affected
    • a4d5613c4dc6d413e0733e37db9d116a2a36b9f3 and later · before ed95b1e88174566de3dc81d94399aacf2c9dfba4affected · git
    • a4d5613c4dc6d413e0733e37db9d116a2a36b9f3 and later · before 0c027c2bad7f5111c51a358b5d392e1a695dabffaffected · git
    • a4d5613c4dc6d413e0733e37db9d116a2a36b9f3 and later · before 9f7ddc222cae8254e93d5c169a8ae11a49d912a7affected · git
    • a4d5613c4dc6d413e0733e37db9d116a2a36b9f3 and later · before fb3a122a978626b33de3367ee1762da934c0f512affected · git
    • a4d5613c4dc6d413e0733e37db9d116a2a36b9f3 and later · before 0c66c6f4e21cb22220cbd8821c5c73fc157d20dcaffected · git
    • 5.4.167 and later · before 5.5affected · semver
    • 5.10.87 and later · before 5.11affected · semver
    • before 5.14not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.37.1.el9_47.3.0-427.37.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.37.1.el9_45.14.0-427.37.1.el9_4

+96

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-26935May 1, 2024 · scsi: core: Fix unremoved procfs host directory regression
    22Monitor
  • ← EarlierCVE-2024-26937May 1, 2024 · drm/i915/gt: Reset queue_priority_hint on parking
    22Monitor
  • Later →CVE-2024-26948May 1, 2024 · drm/amd/display: Add a dc_state NULL check in dc_state_release
    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 Linux0c027c2bad7f5111c51a358b5d392e1a695dabffVendor (CNA)
Linux Linux0c66c6f4e21cb22220cbd8821c5c73fc157d20dcVendor (CNA)
Linux Linux5.11Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux9f7ddc222cae8254e93d5c169a8ae11a49d912a7Vendor (CNA)
Linux Linuxed95b1e88174566de3dc81d94399aacf2c9dfba4Vendor (CNA)
Linux Linuxfb3a122a978626b33de3367ee1762da934c0f512Vendor (CNA)
azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 hyperv-daemons 6.6.35.1-1 on Azure Linux 3.06.6.35.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.3.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.37.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.7.12-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.77.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)

+4

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.

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

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.

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

Change log

  1. Fix✗ → ✓

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

References

All records