CVE-2022-49659 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits In commit 1be37d3b0414 ("can: m_can: fix periph RX path: use rx-offload to ensure skbs are sent from softirq context") the RX path for peripheral devices was switched to RX-offload. Received CAN frames are pushed to RX-offload together with a timestamp. RX-offload is designed to handle overflows of the timestamp correctly, if 32 bit timestamps are provided. The timestamps of m_can core are only 16 bits wide. So this patch shifts them to full 32 bit before passing them to RX-offload.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-07	0.03%	0.07%	+0.04%
2	2026-01-02	0.05%	0.03%	-0.02%
3	2025-11-22	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-07

0.03%

0.07%

+0.04%

2026-01-02

0.05%

0.03%

-0.02%

2025-11-22

—

0.05%

—

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]

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]

OS Trackers for CVE-2022-49659

vendor	priority	summary	link
`debian`	unimportant	CVE-2022-49659 unimportant 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-49659
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49659
`suse`	medium	CVE-2022-49659 severity moderate: SUSE including 53 source package names (bpftool-7.0.0-284.11.1.el9_2, cluster-md-kmp-default, …), 225 product×package rows across 37 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Liberty Linux 9, … (37 product lines)): Known Not Affected 198, Fixed 27.	https://www.suse.com/security/cve/CVE-2022-49659/
`ubuntu`	medium	CVE-2022-49659 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, ignored 146, not-affected 145, released 114, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49659

Affected software / configurations for CVE-2022-49659

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.13, < 5.15.54	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.18.11	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc1::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc2::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc3::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc4::::::
linux	linux_kernel	5.19	cpe:2.3:o:linux:linux_kernel:5.19:rc5::::::

References for CVE-2022-49659

URL	Tags
https://git.kernel.org/stable/c/2a2914a5bd7f38efe55a8372178146de82e0bce9	Patch
https://git.kernel.org/stable/c/4c3333693f07313f5f0145a922f14a7d3c0f4f21	Patch
https://git.kernel.org/stable/c/c7333f79888497bfd75dcd02a94eaf836dd1042c	Patch

URL

CVE-2022-49659 | can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits

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

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

Weakness enumeration for CVE-2022-49659

OS Trackers for CVE-2022-49659

Affected software / configurations for CVE-2022-49659

References for CVE-2022-49659