CVE-2022-41858: Null Pointer Dereference

Published Apr 5, 2022
·
Updated

A flaw was found in the Linux kernel. A NULL pointer dereference may occur while a slip driver is in progress to detach in sltxtimeout in drivers/net/slip/slip.c. This issue could allow an attacker to crash the system or leak internal kernel information.

Other sources

Linux Kernel is vulnerable to a denial of service, caused by a NULL pointer dereference flaw when a slip driver is in progress to detach in sltxtimeout in drivers/net/slip/slip.c. By sending a specially-crafted request to simulate slip network card from user-space of linux, a remote attacker could exploit this vulnerability to cause the system to crash or obtain internal kernel information.

IBM

There are null-ptr-deref vulnerabilities in drivers/net/slip of linux that allow attacker to crash linux kernel by simulating slip network card from user-space of linux.

------------------------------------------

[Root cause]

When a slip driver is detaching, the slipclose() will act to cleanup necessary resources and sl->tty is set to NULL in slipclose(). Meanwhile, the packet we transmit is blocked, sltxtimeout() will be called. Although slipclose() and sltxtimeout() use sl->lock to synchronize, we dont judge whether sl->tty equals to NULL in sltxtimeout() and the null pointer dereference bug will happen.

(Thread 1) | (Thread 2) | slipclose() | spinlockbh(&sl->lock) | ... ... | sl->tty = NULL //(1) sltxtimeout() | spinunlockbh(&sl->lock) spinlock(&sl->lock); | ... | ... ttycharsinbuffer(sl->tty)| if (tty->ops->..) //(2) | ... | synchronizercu()

We set NULL to sl->tty in position (1) and dereference sl->tty in position (2).

------------------------------------------

Red Hat

Affected Software

16 affected componentsFixes available
redhat/kernel<5.18
5.18
Linux Linux kernel<4.9.311
Linux Linux kernel>=4.10<4.14.276
Linux Linux kernel>=4.15<4.19.239
Linux Linux kernel>=4.20<5.4.190
Linux Linux kernel>=5.5.0<5.10.112
Linux Linux kernel>=5.11<5.15.35
Linux Linux kernel>=5.16<5.17.4
NetApp Hci Baseboard Management Controller=h300s
NetApp Hci Baseboard Management Controller=h410c
NetApp Hci Baseboard Management Controller=h410s
NetApp Hci Baseboard Management Controller=h500s
NetApp Hci Baseboard Management Controller=h700s
IBM Security Verify Governance, Identity Manager software component<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager virtual appliance component<=ISVG 10.0.2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.133-16.12.21-16.12.22-1

Remediation

Information

This flaw can be mitigated by preventing the affected slip driver from loading during the boot time, and ensuring the module is added to the blacklist file. ~~~ Refer: How do I blacklist a kernel module to prevent it from loading automatically? https://access.redhat.com/solutions/41278 ~~~

Event History

Apr 5, 2022
CVE Published
03:30 PM
Data Sourced
03:30 PM
RemedyDescriptionSeverityWeakness
Nov 21, 2022
Data Sourced
via Red Hat·04:02 AM
DescriptionSeverityAffected Software
Jan 17, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Jan 12, 2024
Data Sourced
via Launchpad·12:12 AM
Description
Apr 20, 2025
Data Sourced
via Ubuntu·04:16 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2022-41858?

CVE-2022-41858 is classified as a high severity vulnerability due to its potential to crash the system or leak internal kernel information.

2

How do I fix CVE-2022-41858?

To mitigate CVE-2022-41858, update your Linux kernel to version 5.19 or later, or apply the specific patches provided by your distribution.

3

Which versions of the Linux kernel are affected by CVE-2022-41858?

CVE-2022-41858 affects Linux kernel versions prior to 5.19, specifically versions between 4.10 and 5.18.

4

Can CVE-2022-41858 be exploited remotely?

Yes, an attacker may exploit CVE-2022-41858 remotely if the system has the affected slip driver enabled.

5

What is the impact of CVE-2022-41858 on affected systems?

The impact of CVE-2022-41858 includes the potential for system crashes and unauthorized access to sensitive information within the kernel.

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