data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-74478 in the interactive tracker

CVE-2026-74478

um: vector: fix use-after-free in vector_mmsg_rx()

9.8 EPSS 0.9% AV:N

Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem arch/um. Debian urgency: not yet assigned.

Debian does not build this code. The per-release build detail is under "Where it lives" below.

What to do, per Debian release

Debian's own status for CVE-2026-74478 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormfixedDLA-4777-1 · 2026-09-08 · text6.1.187-1Update the kernel and reboot. DLA-4777-1 shipped the fix on 2026-09-08, in 6.1.187-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixedDSA-6466-1 · 2026-08-25 · text6.12.105-1Update the kernel and reboot. DSA-6466-1 shipped the fix on 2026-08-25, in 6.12.105-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.1.8-1Update the kernel and reboot. Fixed in 7.1.8-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.8-1Update the kernel and reboot. Fixed in 7.1.8-1. A running kernel keeps the old code until the machine restarts.
Debian 12bookworm · linux-6.12fixedDLA-4788-1 · 2026-09-19 · text6.12.107-1~deb12u1Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

When vector_mmsg_rx() discards a packet whose overlay header fails verify_header(), it frees the skb and continues the loop: if (header_check < 0) { dev_kfree_skb_irq(skb); vp->estats.rx_encaps_errors++; continue; } The normal and short-packet paths fall through to the bottom of the loop body, which clears the consumed slot and advances the cursors: (*skbuff_vector) = NULL; mmsg_vector++; skbuff_vector++; The verify_header() < 0 path skips that via continue, so the freed skb is left in skbuff_vector[] and the cursors do not advance. The next iteration reads the same slot, gets the freed skb, and frees it again, producing a refcount underflow / use-after-free in the RX path. Discard the slot the same way the other paths do before continuing. Only transports whose verify_header() can return negative are affected: GRE and L2TPv3 do so on a cookie/session-id mismatch (raw/tap do not), so any peer on such a transport can trigger it without authentication.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

arch/um/drivers/vector_kern.c

What this is
USER-MODE LINUX (UML)MAINTAINERS section matched on arch/um/ · linux-um@lists.infradead.org · Maintained
Kernel module
none to look for. The file would have gone into vector, and Debian does not compile it into that module, so finding vector in lsmod would say nothing about this CVE.

Check it on the machine

grep -w CONFIG_UML_NET_VECTOR /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 5 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

  • bookworm, trixie, forky, sid, bookworm · linux-6.12n
n
not enabled on any flavour - this release does not build the code
Build switch
CONFIG_UML_NET_VECTOR

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-08-15 (2 months ago)source
CVSS
9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it
Attack vector
network (AV:N)source
EPSS
0.86%, higher than 57.9% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
arch/um

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
4.175.10.265967c779c9853
4.175.15.216a7bc015bb798
4.176.1.1837dc9781e320d
4.176.6.1514b9601595e8b
4.176.12.10367d58ab4f2cc
4.176.18.44180ff4c81faf
4.177.1.8804b681002ea
4.177.2af421e9aed39

Debian advisories

AdvisoryDateShipped toDebian
DLA-4788-12026-09-19bookworm 6.12.107-1~deb12u1tracker
DLA-4777-12026-09-08bookworm 6.1.187-1tracker
DSA-6466-12026-08-25trixie 6.12.105-1tracker

Why the CNA scored it this way

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:NAttack vector, network
The bug is reached from remotely sent GRE or L2TPv3 packets processed by vector_mmsg_rx() via recvmmsg on the tunnel socket; the fix commit states any peer on those transports can trigger it without authentication.
AC:LAttack complexity, low
An attacker reliably triggers verify_header() failure with a wrong GRE key or L2TPv3 session/cookie, and sending two or more malformed packets in one recvmmsg batch causes immediate double-free of the same skb without races or special memory layout.
PR:NPrivileges required, none
No privileges on the UML instance are required; exploitation needs only the ability to send network packets on the configured GRE/L2TPv3 transport, and overlay keys/cookies are not authenticated security controls.
UI:NUser interaction, none
Exploitation is driven entirely by remote packets delivered to the vector netdev RX path and requires no victim user or administrator action beyond the interface already being up.
S:UScope, unchanged
The use-after-free corrupts sk_buff memory inside the UML kernel network driver and does not by itself cross a VM, IOMMU, or host-kernel security boundary.
C:HConfidentiality impact, high
The refcount underflow/use-after-free leaves a dangling sk_buff pointer that can be reallocated and read through standard heap grooming, giving an arbitrary kernel memory disclosure primitive.
I:HIntegrity impact, high
Reclaiming the freed sk_buff enables attacker-controlled contents in kernel heap objects and can be leveraged for arbitrary write or control-flow hijack in the UML kernel context.
A:HAvailability impact, high
The double-free in the RX path can immediately oops or panic the UML kernel, and an unauthenticated remote peer can retrigger the condition by sending additional malformed tunnel packets.