Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50301

iommu/omap: Fix buffer overflow in debugfs

High7.8EPSS 0.19%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50301, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < 706e359cf046c142db290244c3f4938b20fbe805
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < ec53b99b6b9da8b501f001595a6260c03b42d5b7
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < 648472df221f2bbffb433b964bcb87baccc586d8
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < 4010a1afaae1c0fb9c2cac5de703bed29b1f1782
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < 2fee0dbfaeaaa4bda04279ce772c4572b1429d04
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < 0c7043a5b5c3b35f5dc8875757f71e7f491d64d4
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < bd0438f534b2e31b12f0b39b355c5dc2bbdaf854
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < 9814cc350e0765ce69244bf55ae4c8b29facd27e
    • affected bd4396f09a4a9e77423e92ec9448217ab46f6edf – < 184233a5202786b20220acd2d04ddf909ef18f29
  • Linux · Linux

    • affected 3.19
    • unaffected < 3.19
    • unaffected 4.9.331 – ≤ 4.9.*
    • unaffected 4.14.296 – ≤ 4.14.*
    • unaffected 4.19.262 – ≤ 4.19.*
    • unaffected 5.4.220 – ≤ 5.4.*
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50301 badge
[![CVE-2022-50301](https://trackcve.app/badge/CVE-2022-50301.svg)](https://trackcve.app/cve/CVE-2022-50301)

Record last updated .