LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46943: media: staging/intel-ipu3: Fix set_fmt error handling

In the Linux kernel, the following vulnerability has been resolved: media: staging/intel-ipu3: Fix set_fmt error handling If there in an error during a set_fmt, do not overwrite the previous sizes with the invalid config. Without this patch, v4l2-compliance ends up allocating 4GiB of RAM and causing the following OOPs [ 38.662975] ipu3-imgu 0000:00:05.0: swiotlb buffer is full (sz: 4096 bytes) [ 38.662980] DMA: Out of SW-IOMMU space for 4096 bytes at device 0000:00:05.0 [ 38.663010] general protection fault: 0000 [#1] PREEMPT SMP

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can let an invalid camera/media format setting corrupt stored size values, leading to excessive memory allocation and a kernel crash. The public record describes a local reliability impact in the Intel IPU3 media driver, not remote compromise or confirmed exploitation.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency internet-facing exposure. Patch affected Linux endpoints or appliances during the next appropriate update cycle, with higher priority for systems relying on Intel IPU3 camera/media functions.

Technical view

The vulnerable intel-ipu3 staging media driver overwrote prior valid frame sizes after set_fmt errors. The CVE text reports v4l2-compliance allocating 4 GiB and triggering SW-IOMMU exhaustion followed by a general protection fault. The fix preserves previous sizes when set_fmt fails.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the intel-ipu3 media driver path present or enabled. The provided data lists affected Linux versions and stable commits, but does not identify distributions, configurations, or reachable attack surfaces.

Exploitation context

CISA KEV status is false in the supplied bundle. No cited source reports active exploitation. The available evidence shows a reproducible compliance-test crash condition, but not a weaponized exploit or remote attack path.

Researcher notes

The source bundle lacks CVSS, CWE, distro advisories, and detailed privilege requirements. Analysis should stay close to the kernel commit behavior: failed set_fmt must not replace known-good sizes with invalid configuration values.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the referenced stable fixes.
  • Prioritize systems using Intel IPU3 camera or media processing hardware.
  • Check vendor kernel advisories for exact fixed package versions.
  • If updates are unavailable, follow vendor guidance for interim controls.
  • Track this as reliability and local denial-of-service risk unless new evidence emerges.

Validation and detection

  • Inventory Linux kernel versions against the affected ranges in the CVE record.
  • Confirm installed kernel source or package includes one referenced stable commit.
  • Identify whether intel-ipu3 or ipu3-imgu devices are present and enabled.
  • Review kernel logs for ipu3-imgu, SW-IOMMU exhaustion, or general protection faults.
  • Document distribution-specific fixed versions once vendor advisories are checked.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-46943 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6d5f26f2e045f2377b524516194657c00efbbce8, 6d5f26f2e045f2377b524516194657c00efbbce8, 6d5f26f2e045f2377b524516194657c00efbbce8, 6d5f26f2e045f2377b524516194657c00efbbce8, 6d5f26f2e045f2377b524516194657c00efbbce8unaffected
LinuxLinux5.2, 0, 5.4.118, 5.10.36, 5.11.20, 5.12.3, 5.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.