CVE-2022-50301 [High] | Out-of-bounds Write in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-12-05	0.08%	0.02%	-0.06%
2	2025-09-16	—	0.08%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-12-05

0.08%

0.02%

-0.06%

2025-09-16

—

0.08%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2022-50301

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50301 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-50301
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2022-50301
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50301/
`ubuntu`	medium	CVE-2022-50301 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 160, released 148, not-affected 84, needed 4, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50301

Affected software / configurations for CVE-2022-50301

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.19, < 4.9.331	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.10, < 4.14.296	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.15, < 4.19.262	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.220	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.150	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.75	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.19.17	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.0, < 6.0.3	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-50301

URL	Tags
https://git.kernel.org/stable/c/0c7043a5b5c3b35f5dc8875757f71e7f491d64d4	Patch
https://git.kernel.org/stable/c/184233a5202786b20220acd2d04ddf909ef18f29	Patch
https://git.kernel.org/stable/c/2fee0dbfaeaaa4bda04279ce772c4572b1429d04	Patch
https://git.kernel.org/stable/c/4010a1afaae1c0fb9c2cac5de703bed29b1f1782	Patch
https://git.kernel.org/stable/c/648472df221f2bbffb433b964bcb87baccc586d8	Patch
https://git.kernel.org/stable/c/706e359cf046c142db290244c3f4938b20fbe805	Patch
https://git.kernel.org/stable/c/9814cc350e0765ce69244bf55ae4c8b29facd27e	Patch
https://git.kernel.org/stable/c/bd0438f534b2e31b12f0b39b355c5dc2bbdaf854	Patch
https://git.kernel.org/stable/c/ec53b99b6b9da8b501f001595a6260c03b42d5b7	Patch

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2022-50301

Common vulnerability scoring system (CVSS) metrics for CVE-2022-50301

Weakness enumeration for CVE-2022-50301

OS Trackers for CVE-2022-50301

Affected software / configurations for CVE-2022-50301

References for CVE-2022-50301