CVE-2026-45842: slip: reject VJ receive packets on instances with no rstate array

Published May 27, 2026
·
Updated

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

slip: reject VJ receive packets on instances with no rstate array

slhcinit() accepts rslots == 0 as a valid configuration, with the documented meaning of 'no receive compression'. In that case the allocation loop in slhcinit() is skipped, so comp->rstate stays NULL and comp->rslotlimit stays 0 (from the kzalloc of struct slcompress).

The receive helpers do not defend against that configuration. slhcuncompress() dereferences comp->rstate[x] when the VJ header carries an explicit connection ID, and slhcremember() later assigns cs = &comp->rstate[...] after only comparing the packet's slot number to comp->rslotlimit. Because rslotlimit is 0, slot 0 passes the range check, and the code dereferences a NULL rstate.

The configuration is reachable in-tree through PPP. PPPIOCSMAXCID stores its argument in a signed int, and (val >> 16) uses arithmetic shift. Passing 0xffff0000 therefore sign-extends to -1, so val2 + 1 is 0 and pppgeneric.c ends up calling slhcinit(0, 1). Because /dev/ppp open is gated by nscapable(CAPNETADMIN), the whole path is reachable from an unprivileged user namespace. Once the malformed VJ state is installed, any inbound VJ-compressed or VJ-uncompressed frame that selects slot 0 crashes the kernel in softirq context:

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:slhcuncompress (drivers/net/slip/slhc.c:519) Call Trace: <TASK> pppreceivenonmpframe (drivers/net/ppp/pppgeneric.c:2466) pppinput (drivers/net/ppp/pppgeneric.c:2359) pppasyncprocess (drivers/net/ppp/pppasync.c:492) taskletactioncommon (kernel/softirq.c:926) handlesoftirqs (kernel/softirq.c:623) runksoftirqd (kernel/softirq.c:1055) smpbootthreadfn (kernel/smpboot.c:160) kthread (kernel/kthread.c:436) retfromfork (arch/x86/kernel/process.c:164) </TASK>

Reject the receive side on such instances instead of touching rstate. slhcuncompress() falls through to its existing 'bad' label, which bumps slsierror and enters the toss state. slhcremember() mirrors that with an explicit slsierror increment followed by slhctoss(); the slsirunt counter is not used here because a missing rstate is an internal configuration state, not a runt packet.

The transmit path is unaffected: the only in-tree caller that picks rslots from userspace (pppgeneric.c) still supplies tslots >= 1, and slip.c always calls slhcinit(16, 16), so comp->tstate remains valid and slhccompress() continues to work.

Affected Software

17 affected componentsFixes available
Linux Linux kernel (slip)
Microsoft azl3 kernel 6.6.139.1-1<6.6.141.1-1
6.6.141.1-1
Linux Linux kernel>=2.6.32.70<2.6.33
Linux Linux kernel>=3.2.75<3.3
Linux Linux kernel>=3.4.111<3.5
Linux Linux kernel>=3.10.96<3.11
Linux Linux kernel>=3.12.53<3.13
Linux Linux kernel>=3.14.60<3.15
Linux Linux kernel>=3.18.27<3.19
Linux Linux kernel>=4.1.17<4.2
Linux Linux kernel>=4.3.5<5.10.258
Linux Linux kernel>=5.11<5.15.209
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.141.1-1
  2. Configuration

    Update/align the in-tree PPP/slip logic so the receive path rejects VJ receive packets when the instance has no rstate array (instead of touching comp->rstate) to prevent the NULL pointer dereference described as KASAN: null-ptr-deref in slhc_uncompress() / slhc_remember() (drivers/net/slip/slhc.c:519).

    Linux kernel PPP (slhc: drivers/net/slip/slhc.c / slip: slip.c) Reject VJ receive packets on PPP/slip instances with no receive rstate array (no-rstate configuration) = enabled

Event History

May 27, 2026
CVE Published
via MITRE·09:24 AM
Data Sourced
via MITRE·09:24 AM
Description
Data Sourced
via NVD·11:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
May 28, 2026
Data Sourced
via Microsoft·08:09 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:09 AM
Affected Software
Updated
via Microsoft·08:09 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-45842?

The severity of CVE-2026-45842 is rated at 57, indicating a moderate risk level.

2

How do I fix CVE-2026-45842?

To resolve CVE-2026-45842, ensure that your Linux kernel is updated to the latest version that addresses this vulnerability.

3

What systems are affected by CVE-2026-45842?

CVE-2026-45842 affects instances of the Linux kernel that utilize the slip protocol.

4

What type of vulnerability is CVE-2026-45842?

CVE-2026-45842 is a vulnerability related to incorrectly handling VJ receive packets in the Linux kernel's slip implementation.

5

When was CVE-2026-45842 published?

CVE-2026-45842 was published on May 27, 2026.

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