Kernel memory corruption via OMAP debugfs overflow
Published Sep 15, 2025 · Updated Sep 15, 2025
An out-of-bounds write in affected Linux kernel builds allows local users to corrupt memory through the OMAP IOMMU debugfs interface. In omap2_iommu_dump_ctx(), the first formatted write occurs before len is checked, and snprintf() advances the pointer by the would-have-written length rather than the bytes actually copied. The path requires an OMAP IOMMU build and access to its debugfs files, whose root is restricted to root by default; a short destination buffer can corrupt kernel memory.
Summary
What happened
An out-of-bounds write in affected Linux kernel builds allows local users to corrupt memory through the OMAP IOMMU debugfs interface. In omap2_iommu_dump_ctx(), the first formatted write occurs before len is checked, and snprintf() advances the pointer by the would-have-written length rather than the bytes actually copied. The path requires an OMAP IOMMU build and access to its debugfs files, whose root is restricted to root by default; a short destination buffer can corrupt kernel memory.
The record
- CVE
- CVE-2022-50301
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.19
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <0c7043a5b5c3b35f5dc8875757f71e7f491d64d4
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <184233a5202786b20220acd2d04ddf909ef18f29
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <2fee0dbfaeaaa4bda04279ce772c4572b1429d04
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <4010a1afaae1c0fb9c2cac5de703bed29b1f1782
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <648472df221f2bbffb433b964bcb87baccc586d8
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <706e359cf046c142db290244c3f4938b20fbe805
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <9814cc350e0765ce69244bf55ae4c8b29facd27e
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <bd0438f534b2e31b12f0b39b355c5dc2bbdaf854
- Affected versionversion=bd4396f09a4a9e77423e92ec9448217ab46f6edf <ec53b99b6b9da8b501f001595a6260c03b42d5b7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo