LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48637: bnxt: prevent skb UAF after handing over to PTP worker

In the Linux kernel, the following vulnerability has been resolved: bnxt: prevent skb UAF after handing over to PTP worker When reading the timestamp is required bnxt_tx_int() hands over the ownership of the completed skb to the PTP worker. The skb should not be used afterwards, as the worker may run before the rest of our code and free the skb, leading to a use-after-free. Since dev_kfree_skb_any() accepts NULL make the loss of ownership more obvious and set skb to NULL.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-48637 is a Linux kernel use-after-free bug in the bnxt network driver’s transmit timestamp handling. A completed network buffer can be handed to a PTP worker and then used again after the worker may have freed it. Sources provide no CVSS score or confirmed exploitation.

Executive priority

Medium operational priority unless your environment relies on affected bnxt network paths. No active exploitation is cited, but kernel use-after-free defects can affect system stability and security boundaries, so include it in regular kernel patch cycles.

Technical view

In bnxt_tx_int(), the completed skb is transferred to the PTP worker when timestamp reading is required. The original path could continue using that skb after ownership transfer. The kernel fix makes ownership loss explicit by setting skb to NULL, avoiding later use after a possible free.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the bnxt driver path in use, especially where PTP transmit timestamp handling is relevant. The source bundle lists Linux kernel affected version data but does not provide downstream distribution package status.

Exploitation context

The bundle does not show CISA KEV listing, public exploitation, exploit availability, or attacker prerequisites. Treat this as a kernel memory-safety issue requiring patch tracking, not as confirmed active exploitation.

Researcher notes

Evidence is narrow and upstream-focused. The issue is CWE-416 use-after-free caused by skb ownership transfer to a PTP worker. The bundle names the fix behavior but does not provide crash impact, privilege boundary details, CVSS, or exploitability analysis.

Mitigation direction

  • Check vendor or distribution kernel advisories for CVE-2022-48637 coverage.
  • Upgrade affected Linux kernels to builds containing the referenced stable fixes.
  • Prioritize systems using bnxt networking and PTP timestamping features.
  • If patching is delayed, review vendor guidance for supported operational workarounds.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Confirm whether bnxt driver is loaded or packaged on relevant systems.
  • Verify installed kernels include one of the referenced stable commits or vendor backports.
  • Record distro advisory status because upstream commit presence may differ from package versions.
Prepared
Confidence
medium
Sources
5

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-416: 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-48637 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
4Source links

SSVC decision data

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

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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux83bb623c968e7351aee5111547693f95f330dc5a, 83bb623c968e7351aee5111547693f95f330dc5a, 83bb623c968e7351aee5111547693f95f330dc5aunaffected
LinuxLinux5.14, 0, 5.15.71, 5.19.12, 6.0affected
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.