Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-53232: iommu/s390: Implement blocking domain

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 3be34fa1cdbf180c1a948cfededfdf2cdc497199, bd89d94f3ea6fdaee983cbc69226a00b9bde6d59, ecda483339a5151e3ca30d6b82691ef6f1d17912.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 3be34fa1cdbf180c1a948cfededfdf2cdc497199, bd89d94f3ea6fdaee983cbc69226a00b9bde6d59, ecda483339a5151e3ca30d6b82691ef6f1d17912 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: iommu/s390: Implement blocking domain This fixes a crash when surprise hot-unplugging a PCI device. This crash happens because during hot-unplug __iommu_group_set_domain_nofail() attaching the default domain fails when the platform no longer recognizes the device as it has already been removed and we end up with a NULL domain pointer and UAF. This is exactly the case referred to in the second comment in __iommu_device_set_domain() and just as stated there if we can instead attach the blocking domain the UAF is prevented as this can handle the already removed device. Implement the blocking domain to use this handling. With this change, the crash is fixed but we still hit a warning attempting to change DMA ownership on a blocked device.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th 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
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 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-53232

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 kernel6.7 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

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.7affected
    • c76c067e488ccd55734c3e750799caf2c5956db6 and later · before 3be34fa1cdbf180c1a948cfededfdf2cdc497199affected · git
    • c76c067e488ccd55734c3e750799caf2c5956db6 and later · before bd89d94f3ea6fdaee983cbc69226a00b9bde6d59affected · git
    • c76c067e488ccd55734c3e750799caf2c5956db6 and later · before ecda483339a5151e3ca30d6b82691ef6f1d17912affected · git
    • before 6.7not affected · semver
    • 6.11.11 and later · up to and including 6.11.*not affected · semver
    • 6.12.2 and later · up to and including 6.12.*not affected · semver
    • 6.13 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
Debian:13linuxbefore 6.12.3-16.12.3-1
Red Hat:enterprise_linux:10.0kernelbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64kbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-corebefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debugbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-corebefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-debuginfobefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-develbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-devel-matchedbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modulesbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-corebefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-extrabefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debuginfobefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-develbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-devel-matchedbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modulesbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-corebefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-extrabefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-abi-stablelistsbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-corebefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debugbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debug-corebefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debug-debuginfobefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debug-develbefore 0:6.12.0-55.9.1.el10_00:6.12.0-55.9.1.el10_0

+68

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-53230Dec 27, 2024 · cpufreq: CPPC: Fix possible null-ptr-deref for cppc_get_cpu_cost()
    22Monitor
  • ← EarlierCVE-2024-53231Dec 27, 2024 · cpufreq: CPPC: Fix possible null-ptr-deref for cpufreq_cpu_get_raw()
    22Monitor
  • Later →CVE-2024-53233Dec 27, 2024 · unicode: Fix utf8_load() error path
    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 Linux3be34fa1cdbf180c1a948cfededfdf2cdc497199Vendor (CNA)
Linux Linuxbd89d94f3ea6fdaee983cbc69226a00b9bde6d59Vendor (CNA)
Linux Linuxecda483339a5151e3ca30d6b82691ef6f1d17912Vendor (CNA)
debian:linux6.12.3-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-55.9.1.el10_0 · Red Hat:enterprise_linux:10.0Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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

CWE-416 · Use After Free

CVSS vector

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

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

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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✗ → ✓

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

References

Show all references (2 more)

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

All records