net: bridge: vlan: fix memory leak in __allowed_ingress
Noroxi assessment
Priority: Monitor (action score 30/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: 1.1% (FIRST EPSS); higher than 65.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 14be8d448fca6fe7b2a413831eedd55aef6c6511, 446ff1fc37c74093e81db40811a07b5a19f1d797, c5e216e880fa6f2cd9d4a6541269377657163098.
Low priority for now. Upgrade to Linux Linux 14be8d448fca6fe7b2a413831eedd55aef6c6511, 446ff1fc37c74093e81db40811a07b5a19f1d797, c5e216e880fa6f2cd9d4a6541269377657163098 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: bridge: vlan: fix memory leak in __allowed_ingress When using per-vlan state, if vlan snooping and stats are disabled, untagged or priority-tagged ingress frame will go to check pvid state. If the port state is forwarding and the pvid state is not learning/forwarding, untagged or priority-tagged frame will be dropped but skb memory is not freed. Should free skb when __allowed_ingress returns false.
- Published
- Jun 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 65th percentile
- CWE
- CWE-400
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 kernel5.6 and later · before 5.10.96
- linux linux kernel5.11 and later · before 5.15.19
- linux linux kernel5.16 and later · before 5.16.5
- linux linux kernel5.17
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
- 5.6affected
- a580c76d534c7360ba68042b19cb255e8420e987 and later · before 446ff1fc37c74093e81db40811a07b5a19f1d797affected · git
- a580c76d534c7360ba68042b19cb255e8420e987 and later · before c5e216e880fa6f2cd9d4a6541269377657163098affected · git
- a580c76d534c7360ba68042b19cb255e8420e987 and later · before 14be8d448fca6fe7b2a413831eedd55aef6c6511affected · git
- a580c76d534c7360ba68042b19cb255e8420e987 and later · before fd20d9738395cf8e27d0a17eba34169699fccdffaffected · git
- before 5.6not affected · semver
- 5.10.96 and later · up to and including 5.10.*not affected · semver
- 5.15.19 and later · up to and including 5.15.*not affected · semver
- 5.16.5 and later · up to and including 5.16.*not affected · semver
- 5.17 and laternot affected · original_commit_for_fix
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.16.7-1 | 5.16.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-48746Jun 20, 2024 · net/mlx5e: Fix handling of wrong devices during bond netevent22Monitor
- ← EarlierCVE-2022-48747Jun 20, 2024 · block: Fix wrong offset in bio_truncate()30Monitor
- Later →CVE-2022-48749Jun 20, 2024 · drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc22Monitor
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 | 14be8d448fca6fe7b2a413831eedd55aef6c6511 | Vendor (CNA) |
| Linux Linux | 446ff1fc37c74093e81db40811a07b5a19f1d797 | Vendor (CNA) |
| Linux Linux | c5e216e880fa6f2cd9d4a6541269377657163098 | Vendor (CNA) |
| Linux Linux | fd20d9738395cf8e27d0a17eba34169699fccdff | Vendor (CNA) |
| debian:linux | 5.16.7-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- CVE-2024-394625 days apartclk: bcm: dvp: Assign ->num before accessing ->hws39Monitor
- CVE-2021-44405 days apartx86/xen: Drop USERGS_SYSRET64 paravirt call35Monitor
- CVE-2021-4731330 days apartcpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init33Monitor
- CVE-2024-386161 days apartwifi: carl9170: re-fix fortified-memset warning32Monitor
- CVE-2021-47023113 days apartnet: marvell: prestera: fix port event handling on init32Monitor
- CVE-2022-487160 days apartASoC: codecs: wcd938x: fix incorrect used of portid31Monitor
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.