CVE-2022-49478 [High] | Memory Corruption in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init Syzbot reported that -1 is used as array index. The problem was in missing validation check. hdw->unit_number is initialized with -1 and then if init table walk fails this value remains unchanged. Since code blindly uses this member for array indexing adding sanity check is the easiest fix for that. hdw->workpoll initialization moved upper to prevent warning in __flush_work.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-05	0.07%	0.01%	-0.05%
2	2026-04-06	0.01%	0.07%	+0.05%
3	2025-03-18	—	0.01%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-05

0.07%

0.01%

-0.05%

2026-04-06

0.01%

0.07%

+0.05%

2025-03-18

—

0.01%

—

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]
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	134c704f-9b21-4f2e-91b3-4a467353bcc0

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]

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

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2022-49478

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49478 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-49478
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49478
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-49478/
`ubuntu`	medium	CVE-2022-49478 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 151, ignored 149, not-affected 102, needed 4.	https://ubuntu.com/security/CVE-2022-49478

Affected software / configurations for CVE-2022-49478

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 2.6.18, < 4.9.318	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.10, < 4.14.283	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.15, < 4.19.247	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.198	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.121	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.46	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.17.14	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.18, < 5.18.3	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-49478

URL	Tags
https://git.kernel.org/stable/c/1310fc3538dcc375a2f46ef0a438512c2ca32827	Patch
https://git.kernel.org/stable/c/24e807541e4a9263ed928e6ae3498de3ad43bd1e	Patch
https://git.kernel.org/stable/c/2e004fe914b243db41fa96f9e583385f360ea58e	Patch
https://git.kernel.org/stable/c/3309c2c574e13b21b44729f5bdbf21f60189b79a	Patch
https://git.kernel.org/stable/c/4351bfe36aba9fa7dc9d68d498d25d41a0f45e67	Patch
https://git.kernel.org/stable/c/471bec68457aaf981add77b4f590d65dd7da1059	Patch
https://git.kernel.org/stable/c/a3304766d9384886e6d3092c776273526947a2e9	Patch
https://git.kernel.org/stable/c/a3660e06675bccec4bf149c7229ea1d491ba10d7	Patch
https://git.kernel.org/stable/c/f99a8b1ec0eddc2931aeaa4f490277a15b39f511	Patch

URL

CVE-2022-49478 | media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init

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

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

Weakness enumeration for CVE-2022-49478

OS Trackers for CVE-2022-49478

Affected software / configurations for CVE-2022-49478

References for CVE-2022-49478