CVE-2025-21806— net: let net.core.dev_weight always be non-zero
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2025-21806
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
net: let net.core.dev_weight always be non-zero
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: net: let net.core.dev_weight always be non-zero The following problem was encountered during stability test: (NULL net_device): NAPI poll function process_backlog+0x0/0x530 \ returned 1, exceeding its budget of 0. ------------[ cut here ]------------ list_add double add: new=ffff88905f746f48, prev=ffff88905f746f48, \ next=ffff88905f746e40. WARNING: CPU: 18 PID: 5462 at lib/list_debug.c:35 \ __list_add_valid_or_report+0xf3/0x130 CPU: 18 UID: 0 PID: 5462 Comm: ping Kdump: loaded Not tainted 6.13.0-rc7+ RIP: 0010:__list_add_valid_or_report+0xf3/0x130 Call Trace: ? __warn+0xcd/0x250 ? __list_add_valid_or_report+0xf3/0x130 enqueue_to_backlog+0x923/0x1070 netif_rx_internal+0x92/0x2b0 __netif_rx+0x15/0x170 loopback_xmit+0x2ef/0x450 dev_hard_start_xmit+0x103/0x490 __dev_queue_xmit+0xeac/0x1950 ip_finish_output2+0x6cc/0x1620 ip_output+0x161/0x270 ip_push_pending_frames+0x155/0x1a0 raw_sendmsg+0xe13/0x1550 __sys_sendto+0x3bf/0x4e0 __x64_sys_sendto+0xdc/0x1b0 do_syscall_64+0x5b/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e The reproduction command is as follows: sysctl -w net.core.dev_weight=0 ping 127.0.0.1 This is because when the napi's weight is set to 0, process_backlog() may return 0 and clear the NAPI_STATE_SCHED bit of napi->state, causing this napi to be re-polled in net_rx_action() until __do_softirq() times out. Since the NAPI_STATE_SCHED bit has been cleared, napi_schedule_rps() can be retriggered in enqueue_to_backlog(), causing this issue. Making the napi's weight always non-zero solves this problem. Triggering this issue requires system-wide admin (setting is not namespaced).
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于未正确处理net.core.dev_weight，可能导致警告。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2025-21806
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2025-21806
请登录查看更多情报信息。
Same Patch Batch · Linux · 2025-02-27 · 177 CVEs total
| CVE-2025-21756 | 7.8 HIGH | vsock: Keep the binding until socket destruction |
| CVE-2025-21770 | iommu: Fix potential memory leak in iopf_queue_remove_device() | |
| CVE-2025-21761 | openvswitch: use RCU protection in ovs_vport_cmd_fill_info() | |
| CVE-2025-21763 | neighbour: use RCU protection in __neigh_notify() | |
| CVE-2025-21762 | arp: use RCU protection in arp_xmit() | |
| CVE-2025-21764 | ndisc: use RCU protection in ndisc_alloc_skb() | |
| CVE-2025-21765 | ipv6: use RCU protection in ip6_default_advmss() | |
| CVE-2025-21766 | ipv4: use RCU protection in __ip_rt_update_pmtu() | |
| CVE-2025-21767 | clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context | |
| CVE-2025-21769 | ptp: vmclock: Add .owner to vmclock_miscdev_fops | |
| CVE-2025-21768 | net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels | |
| CVE-2025-21771 | sched_ext: Fix incorrect autogroup migration detection | |
| CVE-2025-21776 | USB: hub: Ignore non-compliant devices with too many configs or interfaces | |
| CVE-2025-21781 | batman-adv: fix panic during interface removal | |
| CVE-2025-21780 | drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() | |
| CVE-2025-21779 | KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel | |
| CVE-2025-21778 | tracing: Do not allow mmap() of persistent ring buffer | |
| CVE-2025-21777 | ring-buffer: Validate the persistent meta data subbuf array | |
| CVE-2025-21775 | can: ctucanfd: handle skb allocation failure | |
| CVE-2025-21773 | can: etas_es58x: fix potential NULL pointer dereference on udev->serial |
Showing top 20 of 177 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
Same vendor: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
V. Comments for CVE-2025-21806
No comments yet