CVE-2026-64188

CVE CVE-2026-64188EUVD EUVD-2026-46008Published 2026-07-20T16:27:47.000ZLast changed 2026-08-05T12:39:57.000ZCVSS 7.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() rmnet_dellink() removes the endpoint from the hash table with hlist_del_init_rcu() and then immediately frees it with kfree(). However, RCU readers on the receive path (rmnet_rx_handler -> __rmnet_map_ingress_handler) may still hold a reference to the endpoint and dereference ep->egress_dev after the memory has been freed. The endpoint is a kmalloc-32 object, and the stale read at offset 8 corresponds to the egress_dev pointer. BUG: unable to handle page fault for address: ffffffffde942eef Oops: 0002 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 137 Comm: poc_write Not tainted 7.0.0+ #4 PREEMPTLAZY RIP: 0010:rmnet_vnd_rx_fixup (rmnet_vnd.c:27) Call Trace: <TASK> __rmnet_map_ingress_handler (rmnet_handlers.c:48 rmnet_handlers.c:101) rmnet_rx_handler (rmnet_handlers.c:129 rmnet_handlers.c:235) __netif_receive_skb_core.constprop.0 (net/core/dev.c:6096) __netif_receive_skb_one_core (net/core/dev.c:6208) netif_receive_skb (net/core/dev.c:6467) tun_get_user (drivers/net/tun.c:1955) tun_chr_write_iter (drivers/net/tun.c:2003) vfs_write (fs/read_write.c:688) ksys_write (fs/read_write.c:740) </TASK> Add an rcu_head field to struct rmnet_endpoint and replace kfree() with kfree_rcu() so the endpoint memory remains valid through the RCU grace period. Also remove the rmnet_vnd_dellink() call and inline only the nr_rmnet_devs decrement, since rmnet_vnd_dellink() would set ep->egress_dev to NULL during the grace period, creating a data race with lockless readers.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux ceed73a2cf4aff2921802aa3d21d45280677547d <8b17adf6d4fb6bf61fa4c3f58366a7c082799a71; patch: 7.1; patch: 6.6.144; patch: 6.12.95; patch: 0; ceed73a2cf4aff2921802aa3d21d45280677547d <1078ae8175777e80c9637996fb4a46c55f0ce576; patch: 5.15.211; patch: 5.10.260; ceed73a2cf4aff2921802aa3d21d45280677547d <c4e676c3505c5058922dc1a6f1ded795f6758135; ceed73a2cf4aff2921802aa3d21d45280677547d <f193e38cb257d033060b63f1cfd94af076b3a2ab; ceed73a2cf4aff2921802aa3d21d45280677547d <d00c953a8f69921f484b629801766da68f27f658; patch: 6.18.37; ceed73a2cf4aff2921802aa3d21d45280677547d <310b93246bfec7d4452507e0c15477377ed9f025; patch: 7.0.14; patch: 6.1.177; ceed73a2cf4aff2921802aa3d21d45280677547d <41e06fcc5df0774d212e70c5b503fc769492bce3; ceed73a2cf4aff2921802aa3d21d45280677547d <9918698cf3aee4032e12bb42fd5a951dc465339b; 4.14

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.