Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-46824: iommufd: Require drivers to supply the cache_invalidate_user ops

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.20% (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 89827a4de802765b1ebb401fc1e73a90108c7520, a11dda723c6493bb1853bbc61c093377f96e2d47.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 89827a4de802765b1ebb401fc1e73a90108c7520, a11dda723c6493bb1853bbc61c093377f96e2d47 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: iommufd: Require drivers to supply the cache_invalidate_user ops If drivers don't do this then iommufd will oops invalidation ioctls with something like: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 Mem abort info: ESR = 0x0000000086000004 EC = 0x21: IABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault user pgtable: 4k pages, 48-bit VAs, pgdp=0000000101059000 [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP Modules linked in: CPU: 2 PID: 371 Comm: qemu-system-aar Not tainted 6.8.0-rc7-gde77230ac23a #9 Hardware name: linux,dummy-virt (DT) pstate: 81400809 (Nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=-c) pc : 0x0 lr : iommufd_hwpt_invalidate+0xa4/0x204 sp : ffff800080f3bcc0 x29: ffff800080f3bcf0 x28: ffff0000c369b300 x27: 0000000000000000 x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000 x23: 0000000000000000 x22: 00000000c1e334a0 x21: ffff0000c1e334a0 x20: ffff800080f3bd38 x19: ffff800080f3bd58 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff8240d6d8 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 x8 : 0000001000000002 x7 : 0000fffeac1ec950 x6 : 0000000000000000 x5 : ffff800080f3bd78 x4 : 0000000000000003 x3 : 0000000000000002 x2 : 0000000000000000 x1 : ffff800080f3bcc8 x0 : ffff0000c6034d80 Call trace: 0x0 iommufd_fops_ioctl+0x154/0x274 __arm64_sys_ioctl+0xac/0xf0 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x34/0xb4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x190/0x194 All existing drivers implement this op for nesting, this is mostly a bisection aid.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

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

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

  • 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.

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 kernel6.8 and later · before 6.10.10

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

    • 6.8affected
    • 8c6eabae3807e048b9f17733af5e20500fbf858c and later · before 89827a4de802765b1ebb401fc1e73a90108c7520affected · git
    • 8c6eabae3807e048b9f17733af5e20500fbf858c and later · before a11dda723c6493bb1853bbc61c093377f96e2d47affected · git
    • before 6.8not affected · semver
    • 6.10.10 and later · up to and including 6.10.*not affected · semver
    • 6.11 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.4.0-503.14.1.el9_57.4.0-503.14.1.el9_5
AlmaLinux:9kernelbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64kbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-corebefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-debugbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-develbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-corebefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-cross-headersbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-debugbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-debug-corebefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-debug-develbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-503.14.1.el9_55.14.0-503.14.1.el9_5

+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-46822Sep 27, 2024 · arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry
    22Monitor
  • ← EarlierCVE-2024-46823Sep 27, 2024 · kunit/overflow: Fix UB in overflow_allocation_test
    22Monitor
  • Later →CVE-2024-46825Sep 27, 2024 · wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check
    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 Linux89827a4de802765b1ebb401fc1e73a90108c7520Vendor (CNA)
Linux Linuxa11dda723c6493bb1853bbc61c093377f96e2d47Vendor (CNA)
almalinux:bpftool7.4.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-503.14.1.el9_5 · AlmaLinux:9Package registry (OSV)
debian:linux6.10.11-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.4.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-503.14.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage 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.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

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

Show all references (1 more)

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

All records