Medium 5.5Published Apr 3, 2026

CVE-2026-23460net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect

Updated under an hour ago (Oct 28, 2026, 7:50 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: net/rose: fix NULL pointer dereference in rose_transmit_link on reconnect syzkaller reported a bug [1], and the reproducer is available at [2]. ROSE sockets use four sk->sk_state values: TCP_CLOSE, TCP_LISTEN, TCP_SYN_SENT, and TCP_ESTABLISHED. rose_connect() already rejects calls for TCP_ESTABLISHED (-EISCONN) and TCP_CLOSE with SS_CONNECTING (-ECONNREFUSED), but lacks a check for TCP_SYN_SENT. When rose_connect() is called a second time while the first connection attempt is still in progress (TCP_SYN_SENT), it overwrites rose->neighbour via rose_get_neigh(). If that returns NULL, the socket is left with rose->state == ROSE_STATE_1 but rose->neighbour == NULL. When the socket is subsequently closed, rose_release() sees ROSE_STATE_1 and calls rose_write_internal() -> rose_transmit_link(skb, NULL), causing a NULL pointer dereference. Per connect(2), a second connect() while a connection is already in progress should return -EALREADY. Add this missing check for TCP_SYN_SENT to complete the state validation in rose_connect(). [1] https://syzkaller.appspot.com/bug?extid=d00f90e0af54102fb271 [2] https://gist.github.com/mrpre/9e6779e0d13e2c66779b1653fef80516

CVSS: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: May 11, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before c85fe6580e86947ca07907ebf4363a73c156fda7; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before a753844d2a8136f090123c8fb1ff6c7f6ee7c2b3; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before c2ab74c12932e52cfa1e7e4582d42b0c8bec96c7; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 builds before 0c9fb70a206a8734e10468ecc24d57c7596cf64e; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 508f49ccbe0329641bb681f7d0052bb4e5943252; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 builds before 0c3e8bff808f17ad37a51d8e719eed22c7863120; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before a12254050e3050f1011cd24f3b880a6882d0139d; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before e1f0a18c9564cdb16523c802e2c6fe5874e3d944	CNA record
linux linux_kernel linux:linux_kernel	from 2.6.12.1 before 5.10.253; from 5.11 before 5.15.203; from 5.16 before 6.1.167; from 6.2 before 6.6.130; from 6.7 before 6.12.78; from 6.13 before 6.18.20; from 6.19 before 6.19.10; 2.6.12; and 8 more ranges	NVD

References

References

https://git.kernel.org/stable/c/c85fe6580e86947ca07907ebf4363a73c156fda7	patch
https://git.kernel.org/stable/c/a753844d2a8136f090123c8fb1ff6c7f6ee7c2b3	patch
https://git.kernel.org/stable/c/c2ab74c12932e52cfa1e7e4582d42b0c8bec96c7	patch
https://git.kernel.org/stable/c/0c9fb70a206a8734e10468ecc24d57c7596cf64e	patch
https://git.kernel.org/stable/c/508f49ccbe0329641bb681f7d0052bb4e5943252	patch
https://git.kernel.org/stable/c/0c3e8bff808f17ad37a51d8e719eed22c7863120	patch
https://git.kernel.org/stable/c/a12254050e3050f1011cd24f3b880a6882d0139d	patch
https://git.kernel.org/stable/c/e1f0a18c9564cdb16523c802e2c6fe5874e3d944	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.