CVE-2025-21920 Details
Description
In the Linux kernel, the following vulnerability has been resolved: vlan: enforce underlying device type Currently, VLAN devices can be created on top of non-ethernet devices. Besides the fact that it doesn't make much sense, this also causes a bug which leaks the address of a kernel function to usermode. When creating a VLAN device, we initialize GARP (garp_init_applicant) and MRP (mrp_init_applicant) for the underlying device. As part of the initialization process, we add the multicast address of each applicant to the underlying device, by calling dev_mc_add. __dev_mc_add uses dev->addr_len to determine the length of the new multicast address. This causes an out-of-bounds read if dev->addr_len is greater than 6, since the multicast addresses provided by GARP and MRP are only 6 bytes long. This behaviour can be reproduced using the following commands: ip tunnel add gretest mode ip6gre local ::1 remote ::2 dev lo ip l set up dev gretest ip link add link gretest name vlantest type vlan id 100 Then, the following command will display the address of garp_pdu_rcv: ip maddr show | grep 01:80:c2:00:00:21 Fix the bug by enforcing the type of the underlying device during VLAN device initialization.
A vulnerability in the Linux kernel's handling of VLAN devices has been identified. VLAN devices were previously allowed on non-Ethernet devices, which not only lacked logical sense but also led to a bug that exposed a kernel function address to user mode. This issue arises during the initialization of GARP and MRP applications for the underlying device, where multicast addresses are added. The process can cause an out-of-bounds read if the device's address length exceeds six bytes, as GARP and MRP multicast addresses are only six bytes long. The vulnerability can be reproduced by creating a GRE tunnel, setting it up, and then adding a VLAN device on top of it, which triggers the out-of-bounds read by exposing the address of the GARP PDU receive function.
The vulnerability has been addressed by modifying the VLAN device initialization process to enforce the correct type for the underlying device, preventing the creation of VLANs on non-Ethernet devices.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 1, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-125 | Out-of-bounds Read | [email protected] |
| CWE-125 | Out-of-bounds Read | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 2.6.35, < 5.4.291 >= 5.5, < 5.10.235 >= 5.11, < 5.15.179 >= 5.16, < 6.1.131 >= 6.2, < 6.6.83 >= 6.7, < 6.12.19 >= 6.13, < 6.13.7 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc4 6.14 rc5 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 3, 2025 | CVE Modified | CVE |
| Oct 1, 2025 | CVE Modified | CISA-ADP |
| Apr 11, 2025 | Initial Analysis | [email protected] |
| Apr 1, 2025 | New CVE Received | kernel.org |