CVE-2025-21925 — llc: do not use skb_get() before dev_queue_xmit()
In the Linux kernel, the following vulnerability has been resolved: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: <TASK> __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 2.6.12≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 64e6a754d33d31aa844b3ee66fb93ac84ca1565e≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 056e8a46d79e22983bae4267e0d9c52927076f46≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 0f764208dc24ea043c3e20194d32aebf94f8459c≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 416e8b4c20c6398044e93008deefd563289f477d≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 17f86e25431ebc15aa9245ff156414fdad47822d≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 9b6f083db141ece0024be01526aa05aa978811cb≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 13f3f872627f0f27c31245524fc11367756240ad and 1 more≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < cd1c44327bbbd50fc24f2b38892f5f328b784d0f |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 6.14-rc2version 6.14-rc5version 6.14-rc4version 6.14-rc3≥ 2.6.13 and < 5.4.291version 6.14-rc1version 2.6.12-rc5version 2.6.12-rc4 and 9 moreversion 2.6.12-rc3version 2.6.12-rc2version 2.6.12≥ 6.13 and < 6.13.7≥ 6.7 and < 6.12.19≥ 6.2 and < 6.6.83≥ 5.16 and < 6.1.131≥ 5.11 and < 5.15.179≥ 5.5 and < 5.10.235 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
12 on the record
- git.kernel.org/stable/c/64e6a754d33d31aa844b3ee66fb93ac84ca1565e
- git.kernel.org/stable/c/17f86e25431ebc15aa9245ff156414fdad47822d
- git.kernel.org/stable/c/9b6f083db141ece0024be01526aa05aa978811cb
- git.kernel.org/stable/c/416e8b4c20c6398044e93008deefd563289f477d
- git.kernel.org/stable/c/13f3f872627f0f27c31245524fc11367756240ad
- git.kernel.org/stable/c/0f764208dc24ea043c3e20194d32aebf94f8459c
- git.kernel.org/stable/c/cd1c44327bbbd50fc24f2b38892f5f328b784d0f
- git.kernel.org/stable/c/056e8a46d79e22983bae4267e0d9c52927076f46
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- cert-portal.siemens.com/productcert/html/ssa-019113.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 12h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 12h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-21925 is "llc: do not use skb_get() before dev_queue_xmit()", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.