CVE-2026-74479net: pktgen: fix proc entry use-after-free
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net: pktgen: fix proc entry use-after-free pktgen_change_name() replaces pkt_dev->entry while holding t->if_lock. pktgen_remove_device() removes the same entry before _rem_dev_from_if_list() takes that lock. This allows the following interleaving: CPU 0 (NETDEV_CHANGENAME) CPU 1 (kpktgend) if_lock(t) proc_remove(pkt_dev->entry) proc_remove(pkt_dev->entry) pkt_dev->entry = proc_create_data(...) if_unlock(t) The kthread can pass the stale proc_dir_entry to proc_remove() after the rename path has freed it. A reproducer with a widened race window reports: BUG: KASAN: slab-use-after-free in proc_remove+0x78/0x80 Read of size 8 at addr ffff8881478fea70 by task kpktgend_0/67 Call Trace: proc_remove+0x78/0x80 pktgen_remove_device.isra.0+0x11c/0x4c0 pktgen_thread_worker+0x1214/0x6bc0 kthread+0x2c6/0x3b0 Allocated by task 95: __proc_create+0x204/0x790 proc_create_data+0x72/0xe0 pktgen_thread_write+0xd61/0x1510 Freed by task 28: kmem_cache_free+0xcb/0x3d0 proc_free_inode+0x5b/0x80 rcu_core+0x50a/0x1850 The buggy address belongs to the object at ffff8881478fea00 which belongs to the cache proc_dir_entry of size 192 Move proc_remove() into the if_lock-protected list removal helper. Keep it before list_del_rcu() to preserve the ordering required by add_device(). The rename path must then finish replacing the entry before removal, or it observes that the device is no longer on the list.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
- Received
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 39df232f1a9ba48d41c68ee7d4046756e709cf91 before 82ed3db9269cb61e3c15bad2f6e221efce90e1e0; from 39df232f1a9ba48d41c68ee7d4046756e709cf91 before d1cc9797cf8f7aeb87e7ad01b748c6a960a819e4; from 39df232f1a9ba48d41c68ee7d4046756e709cf91 before 7991c7cff8b8622cddb3d8dee07dbe74aa4cbec4; from 39df232f1a9ba48d41c68ee7d4046756e709cf91 before 577443530cb592d5782a1f79847411a9363a65c8; from 39df232f1a9ba48d41c68ee7d4046756e709cf91 before f85a58340b91f225de3299dfa782c6414098077c; 39df232f1a9ba48d41c68ee7d4046756e709cf91 builds before 4ef801b838d85c0ea5852c50667f7344ce3b6cd0; from 39df232f1a9ba48d41c68ee7d4046756e709cf91 before b006a5404470bd3eb2aa0425fc447183032047ef; from 39df232f1a9ba48d41c68ee7d4046756e709cf91 before 817ff6efdb7f484ea547218e11e17d8e43daa3b4 | CNA record |
References
- https://git.kernel.org/stable/c/82ed3db9269cb61e3c15bad2f6e221efce90e1e0
- https://git.kernel.org/stable/c/d1cc9797cf8f7aeb87e7ad01b748c6a960a819e4
- https://git.kernel.org/stable/c/7991c7cff8b8622cddb3d8dee07dbe74aa4cbec4
- https://git.kernel.org/stable/c/577443530cb592d5782a1f79847411a9363a65c8
- https://git.kernel.org/stable/c/f85a58340b91f225de3299dfa782c6414098077c
- https://git.kernel.org/stable/c/4ef801b838d85c0ea5852c50667f7344ce3b6cd0
- https://git.kernel.org/stable/c/b006a5404470bd3eb2aa0425fc447183032047ef
- https://git.kernel.org/stable/c/817ff6efdb7f484ea547218e11e17d8e43daa3b4
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.