CVE-2022-48964: ravb: Fix potential use-after-free in ravb_rx_gbeth()
In the Linux kernel, the following vulnerability has been resolved:
ravb: Fix potential use-after-free in ravb_rx_gbeth()
The skb is delivered to napi_gro_receive() which may free it, after calling this,
dereferencing skb may trigger use-after-free.
Security readout for executives and security teams
Plain-English summary
CVE-2022-48964 is a Linux kernel bug in the ravb network driver. A packet buffer may be used after it has been handed to code that can free it. Business risk depends on whether affected kernels and this driver are present; the source bundle does not provide CVSS, impact rating, or exploit evidence.
Executive priority
Track as a focused kernel maintenance item, not an emergency based on the provided evidence. Prioritize assets using the ravb driver or affected embedded kernels, and require confirmation that vendor kernel updates or backports include the fix.
Technical view
The flaw is a potential use-after-free in ravb_rx_gbeth(). After skb is delivered to napi_gro_receive(), that call may free it, so later dereferencing skb can trigger unsafe memory access. The public record points to Linux stable commits as the resolution but does not describe attacker prerequisites or reliable exploitability.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or downstream builds containing the vulnerable ravb driver code. The bundle lists Linux 5.16, 6.0.13, and 6.1 as affected, but does not map downstream distribution packages or appliance firmware.
Exploitation context
The source bundle does not report active exploitation, and CISA KEV status is false. It also does not provide exploit details, attack complexity, privileges required, or whether remote traffic alone can trigger the issue. Treat exploitability as unproven from these sources.
Researcher notes
Evidence is narrow: the record describes a use-after-free pattern and links two stable kernel commits. No CVSS, CWE, exploit status, triggering conditions, or downstream package mapping is included. Validation should focus on code lineage, driver presence, and vendor backport confirmation.
Mitigation direction
Apply vendor kernel updates that include the linked Linux stable fixes.
Check distribution advisories for backported fixes to supported kernel packages.
Prioritize systems where the ravb driver is present and enabled.
If patching is delayed, review vendor guidance for driver-specific mitigations.
Validation and detection
Inventory Linux kernel versions against the affected versions listed in the CVE bundle.
Check whether the ravb driver is built, loaded, or required on each system.
Confirm installed kernel packages include the referenced stable commits or vendor backports.
Review kernel logs for ravb-related crashes while treating logs as non-definitive.
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-48964 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.