LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48639: net: sched: fix possible refcount leak in tc_new_tfilter()

In the Linux kernel, the following vulnerability has been resolved: net: sched: fix possible refcount leak in tc_new_tfilter() tfilter_put need to be called to put the refount got by tp->ops->get to avoid possible refcount leak when chain->tmplt_ops != NULL and chain->tmplt_ops != tp->ops.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in traffic-control filter handling that can leak an internal reference count. The public record does not provide a CVSS score, exploit status, or detailed business impact. Treat it as a kernel maintenance risk: prioritize systems on affected kernels and apply vendor kernel updates rather than assuming emergency exploitation.

Executive priority

Moderate operational priority until more impact data is available. It is a kernel correctness bug with unknown severity and no cited active exploitation. Include it in routine kernel patch cycles, escalating only for sensitive or multi-tenant Linux environments.

Technical view

The flaw is in net/sched tc_new_tfilter(). A reference obtained through tp->ops->get may not be released with tfilter_put() when chain->tmplt_ops is set and differs from tp->ops. The result is a possible refcount leak in kernel traffic-control filter creation logic.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions. The source bundle names Linux as affected and references stable kernel fixes. It does not define affected distributions, package versions, required privileges, or whether default configurations are reachable.

Exploitation context

The provided sources do not show active exploitation, and KEV status is false. No public exploit, attack path, or prerequisite details are included in the bundle. The risk should be assessed through kernel version exposure and vendor advisories.

Researcher notes

The public description supports a refcount-leak condition, but not exploitability, privilege requirements, denial-of-service impact, or affected distribution mapping. Analysis should focus on the stable commits and downstream vendor backports before making exposure claims.

Mitigation direction

  • Inventory Linux kernel versions across servers, containers, appliances, and cloud images.
  • Apply vendor kernel updates that include the referenced stable fixes.
  • Prioritize internet-facing or multi-tenant Linux systems if affected.
  • Check distribution advisories for package-specific fixed versions.
  • Reboot or live-patch according to normal kernel update procedures.

Validation and detection

  • Compare running kernel versions against vendor fixed package guidance.
  • Confirm the deployed kernel includes one of the referenced stable fixes.
  • Review vulnerability scanner findings for CVE-2022-48639 accuracy.
  • Check whether systems use Linux traffic-control filter functionality.
  • Document exceptions where vendor packages are not yet available.
Prepared
Confidence
medium
Sources
7

Public sources used

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.

cve · low confidence lookup

CVE-2022-48639 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

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

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
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7d5509fa0d3ddfe252b4418513e493ac98de3317, 7d5509fa0d3ddfe252b4418513e493ac98de3317, 7d5509fa0d3ddfe252b4418513e493ac98de3317, 7d5509fa0d3ddfe252b4418513e493ac98de3317, 7d5509fa0d3ddfe252b4418513e493ac98de3317unaffected
LinuxLinux5.1, 0, 5.4.215, 5.10.146, 5.15.71, 5.19.12, 6.0affected
Weakness

CWE details

No CWE listed

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