CVE-2022-48977: can: af_can: fix NULL pointer dereference in can_rcv_filter

Published Oct 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

can: afcan: fix NULL pointer dereference in canrcvfilter

Analogue to commit 8aa59e355949 ("can: afcan: fix NULL pointer dereference in canrxregister()") we need to check for a missing initialization of mlpriv in the receive path of CAN frames.

Since commit 4e096a18867a ("net: introduce CAN specific pointer in the struct netdevice") the check for dev->type to be ARPHRDCAN is not sufficient anymore since bonding or tun netdevices claim to be CAN devices but do not initialize mlpriv accordingly.

Affected Software

12 affected components
Linux Linux kernel>=5.4.110<5.4.227
Linux Linux kernel>=5.10.28<5.10.159
Linux Linux kernel>=5.11.12<5.15.83
Linux Linux kernel>=5.16<6.0.13
Linux Linux kernel=6.1-rc1
Linux Linux kernel=6.1-rc2
Linux Linux kernel=6.1-rc3
Linux Linux kernel=6.1-rc4
Linux Linux kernel=6.1-rc5
Linux Linux kernel=6.1-rc6
Linux Linux kernel=6.1-rc7
Linux Linux kernel=6.1-rc8

Event History

Oct 21, 2024
CVE Published
via MITRE·08:05 PM
Data Sourced
via MITRE·08:05 PM
Description
Data Sourced
via NVD·08:15 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2022-48977?

CVE-2022-48977 has been rated as a medium severity vulnerability affecting the Linux kernel.

2

How do I fix CVE-2022-48977?

To fix CVE-2022-48977, users should update to a patched version of the Linux kernel that addresses this vulnerability.

3

What versions of the Linux kernel are affected by CVE-2022-48977?

CVE-2022-48977 affects Linux kernel versions between 5.4.110 and 5.4.227, 5.10.28 to 5.10.159, 5.11.12 to 5.15.83, and 5.16 to 6.0.13, as well as various 6.1 release candidates.

4

What causes the vulnerability CVE-2022-48977?

CVE-2022-48977 is caused by a NULL pointer dereference in the can_rcv_filter function in the Linux kernel.

5

Is CVE-2022-48977 exploitable remotely?

CVE-2022-48977 can potentially be exploited remotely depending on the configuration of the affected systems and how they handle CAN (Controller Area Network) traffic.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203