CVE-2021-47160: net: dsa: mt7530: fix VLAN traffic leaks
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 474a2ddaa192777522a7499784f1d60691cd831a, 4fe4e1f48ba119bdbc7c897c83b04ba0d08f5488, 82ae35b6c14feae5f216913d5b433e143c756d4e.
Low priority for now. Upgrade to Linux Linux 474a2ddaa192777522a7499784f1d60691cd831a, 4fe4e1f48ba119bdbc7c897c83b04ba0d08f5488, 82ae35b6c14feae5f216913d5b433e143c756d4e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: net: dsa: mt7530: fix VLAN traffic leaks PCR_MATRIX field was set to all 1's when VLAN filtering is enabled, but was not reset when it is disabled, which may cause traffic leaks: ip link add br0 type bridge vlan_filtering 1 ip link add br1 type bridge vlan_filtering 1 ip link set swp0 master br0 ip link set swp1 master br1 ip link set br0 type bridge vlan_filtering 0 ip link set br1 type bridge vlan_filtering 0 # traffic in br0 and br1 will start leaking to each other As port_bridge_{add,del} have set up PCR_MATRIX properly, remove the PCR_MATRIX write from mt7530_port_set_vlan_aware.
- Published
- Mar 25, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.1
- CNA · Linux
- 8.1
- 1.0 point gap
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.16 and later · before 4.19.193
- linux linux kernel4.20 and later · before 5.4.124
- linux linux kernel5.5 and later · before 5.10.42
- linux linux kernel5.11 and later · before 5.12.9
- linux linux kernel5.13
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.16affected
- 83163f7dca5684816d01c8ccf4857aa74801e7b7 and later · before ae389812733b1b1e8e07fcc238e41db166b5c78daffected · git
- 83163f7dca5684816d01c8ccf4857aa74801e7b7 and later · before 4fe4e1f48ba119bdbc7c897c83b04ba0d08f5488affected · git
- 83163f7dca5684816d01c8ccf4857aa74801e7b7 and later · before b91117b66fe875723a4e79ec6263526fffdb44d2affected · git
- 83163f7dca5684816d01c8ccf4857aa74801e7b7 and later · before 82ae35b6c14feae5f216913d5b433e143c756d4eaffected · git
- 83163f7dca5684816d01c8ccf4857aa74801e7b7 and later · before 474a2ddaa192777522a7499784f1d60691cd831aaffected · git
- before 4.16not affected · semver
- 4.19.193 and later · up to and including 4.19.*not affected · semver
- 5.4.124 and later · up to and including 5.4.*not affected · semver
- 5.10.42 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.14.6-1 | 5.14.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47158Mar 25, 2024 · net: dsa: sja1105: add error handling in sja1105_setup()22Monitor
- ← EarlierCVE-2021-47159Mar 25, 2024 · net: dsa: fix a crash if ->get_sset_count() fails22Monitor
- Later →CVE-2021-47161Mar 25, 2024 · spi: spi-fsl-dspi: Fix a resource leak in an error handling path22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 474a2ddaa192777522a7499784f1d60691cd831a | Vendor (CNA) |
| Linux Linux | 4fe4e1f48ba119bdbc7c897c83b04ba0d08f5488 | Vendor (CNA) |
| Linux Linux | 82ae35b6c14feae5f216913d5b433e143c756d4e | Vendor (CNA) |
| Linux Linux | ae389812733b1b1e8e07fcc238e41db166b5c78d | Vendor (CNA) |
| Linux Linux | b91117b66fe875723a4e79ec6263526fffdb44d2 | Vendor (CNA) |
| debian:linux | 5.14.6-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.