LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48748: net: bridge: vlan: fix memory leak in __allowed_ingress

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can leak packet memory in specific bridge VLAN handling. An attacker able to send suitable traffic to an affected Linux bridge could consume memory and degrade or deny service. The available sources describe availability impact only, not data theft or code execution.

Executive priority

Prioritize remediation for Linux-based network infrastructure that bridges VLAN traffic. The main business risk is service disruption from memory exhaustion, not confidentiality loss. Patch through normal emergency or accelerated infrastructure maintenance depending on exposure.

Technical view

The bug is in Linux bridge VLAN ingress handling in __allowed_ingress. With per-VLAN state, VLAN snooping and stats disabled, certain untagged or priority-tagged frames are dropped without freeing the skb when PVID state blocks forwarding or learning, causing a memory leak.

Likely exposure

Exposure is most relevant to Linux systems using kernel bridge VLAN features, especially network appliances, virtualization hosts, or servers bridging VLAN traffic. Systems not using Linux bridge VLAN ingress paths are less likely exposed. The bundle does not identify distributions or downstream package names.

Exploitation context

The CVSS vector indicates network, low-complexity, unauthenticated availability impact. The bundle states KEV is false and provides no cited evidence of active exploitation. Treat exploitation status as unconfirmed, not actively exploited.

Researcher notes

Evidence is limited to the CVE description and Linux stable commit references. The affected version data in the bundle is sparse, so downstream kernel package validation should rely on vendor advisories and commit backports rather than version strings alone.

Mitigation direction

  • Check vendor kernel advisories for your distribution or appliance.
  • Update to a kernel containing one of the referenced stable fixes.
  • Prioritize internet- or untrusted-network-facing Linux bridges using VLAN filtering.
  • Temporarily reduce exposure of affected bridge VLAN paths where patching is delayed.
  • Monitor memory pressure and packet-drop symptoms on suspected bridge hosts.

Validation and detection

  • Inventory Linux systems using bridge VLAN or related network appliance functions.
  • Map running kernel versions against vendor advisories and referenced stable commits.
  • Confirm whether VLAN snooping, stats, per-VLAN state, and PVID behavior match exposure conditions.
  • Review operational monitoring for unexplained memory growth on bridge hosts.
  • Verify patched kernels include the relevant stable commit for their branch.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-48748 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-48748Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa580c76d534c7360ba68042b19cb255e8420e987, a580c76d534c7360ba68042b19cb255e8420e987, a580c76d534c7360ba68042b19cb255e8420e987, a580c76d534c7360ba68042b19cb255e8420e987unaffected
LinuxLinux5.6, 0, 5.10.96, 5.15.19, 5.16.5, 5.17affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.