LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50301: iommu/omap: Fix buffer overflow in debugfs

In the Linux kernel, the following vulnerability has been resolved: iommu/omap: Fix buffer overflow in debugfs There are two issues here: 1) The "len" variable needs to be checked before the very first write. Otherwise if omap2_iommu_dump_ctx() with "bytes" less than 32 it is a buffer overflow. 2) The snprintf() function returns the number of bytes that *would* have been copied if there were enough space. But we want to know the number of bytes which were *actually* copied so use scnprintf() instead.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the OMAP IOMMU debugfs code. A small output buffer could be overwritten during context dumping. The public record does not provide a CVSS score, attack prerequisites, or confirmed real-world exploitation, so urgency should be based on whether affected OMAP-based systems are in scope.

Executive priority

Treat this as a targeted kernel maintenance item, not a confirmed emergency. Prioritize embedded or OMAP-based environments first, especially where debug interfaces are enabled. Escalate if a vendor rates it highly for your deployed platform.

Technical view

The fix addresses two length-handling bugs in omap2_iommu_dump_ctx(): checking len before the first write and replacing snprintf() with scnprintf() to track actual copied bytes. The issue is described as a buffer overflow in debugfs and is resolved through upstream stable kernel commits.

Likely exposure

Likely limited to Linux systems using affected kernels and the OMAP IOMMU debugfs path. The source bundle lists Linux kernel versions and stable commits, but does not identify specific distributions, devices, default configurations, or remote exposure.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit use, or a complete attack path. Because the bug is in debugfs, practical exposure likely depends on kernel configuration and access to that interface, but prerequisites are not fully documented here.

Researcher notes

Evidence is strong for the code defect and upstream fix, but incomplete for severity, exploitability, and affected downstream products. Avoid assuming internet exposure or privilege impact from the CVE record alone. Validate configuration and vendor backport status before risk-ranking assets.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-50301 coverage.
  • Update to a kernel release containing the applicable upstream stable fix.
  • Prioritize OMAP-based devices and kernels with debugfs enabled.
  • Restrict unnecessary debugfs access according to existing hardening policy.
  • Track distribution backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions across OMAP or embedded Linux assets.
  • Confirm whether the OMAP IOMMU driver is present and used.
  • Check whether debugfs is enabled or accessible on affected systems.
  • Map installed kernels to vendor advisories or referenced stable commits.
  • Verify remediation through vendor package metadata or kernel changelog evidence.
Prepared
Confidence
medium
Sources
11

Public sources used

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-2022-50301 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
0ADP providers
10Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edf, bd4396f09a4a9e77423e92ec9448217ab46f6edfunaffected
LinuxLinux3.19, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

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