CVE-2022-49404 [Medium] | Integer Overflow in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Fix potential integer multiplication overflow errors When multiplying of different types, an overflow is possible even when storing the result in a larger type. This is because the conversion is done after the multiplication. So arithmetic overflow and thus in incorrect value is possible. Correct an instance of this in the inter packet delay calculation. Fix by ensuring one of the operands is u64 which will promote the other to u64 as well ensuring no overflow.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.05%	0.03%	-0.02%
2	2025-11-18	0.02%	0.05%	+0.04%
3	2025-04-20	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.05%

0.03%

-0.02%

2025-11-18

0.02%

0.05%

+0.04%

2025-04-20

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

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

OS Trackers for CVE-2022-49404

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49404 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-49404
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49404
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-49404/
`ubuntu`	medium	CVE-2022-49404 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 148, not-affected 103, needed 4.	https://ubuntu.com/security/CVE-2022-49404

Affected software / configurations for CVE-2022-49404

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.3, < 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-49404

URL	Tags
https://git.kernel.org/stable/c/06039d8afefdbac05bcea5f397188407eba2996d	Patch
https://git.kernel.org/stable/c/252f4afd4557a2e7075f793a5c80fe6dd9e9ee4a	Patch
https://git.kernel.org/stable/c/31dca00d0cc9f4133320d72eb7e3720badc6d6e6	Patch
https://git.kernel.org/stable/c/3f09ec80f115d2875d747ed28adc1773037e0f8b	Patch
https://git.kernel.org/stable/c/79c164e61f818054cd6012e9035701840d895c51	Patch
https://git.kernel.org/stable/c/8858284dd74906fa00f04f0252c75df4893a7959	Patch
https://git.kernel.org/stable/c/a89cb7ddf6a89bab6012e19da38b7cdb26175c19	Patch
https://git.kernel.org/stable/c/ef5ab2e48a5f9960e2352332b7cdb7064bb49032	Patch
https://git.kernel.org/stable/c/f93e91a0372c922c20d5bee260b0f43b4b8a1bee	Patch

URL

CVE-2022-49404 | RDMA/hfi1: Fix potential integer multiplication overflow errors

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

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

Weakness enumeration for CVE-2022-49404

OS Trackers for CVE-2022-49404

Affected software / configurations for CVE-2022-49404

References for CVE-2022-49404